[#894] subsite reverse proxy

[tsteiner]

What might be the solution to the problem below:

Just to further elaborate, we have a number of subprojects at the location Brent specified. For a specific case that's perhaps a little unusual, we have a site at cdrh.unl.edu/quills (currently incorrectly forwarding...) which is run using Cocoon under Tomcat. We are doing a reverse proxy from Apache httpd at cdrh.unl.edu that (if it were set up properly) keeps the user at cdrh.unl.edu/quills.

Keith Nickum Programmer/Analyst II Center for Digital Research in the Humanities 319 LLS, UNL, 68588-4100 (402) 472-4547 knickum2@unl.edu OR knickum.unl@gmail.com PGP Public Key ID: 0x160E08A5

On 7/14/11 11:21 AM, Brent C Baum wrote:

Todd,

I think the CDRH site is ready to go from "test" stage into production using the CMS system. The one problem we have is that there are several sites we've developed that are currently using the cdrh.unl.edu/project_name. Do you have any solutions for getting around having the cdrh.unl.edu site being hosted through CMS while also being able to maintain the project sites on our own servers?

I've cc'd Keith Nickum, who maintains our servers in order for him to be included on the discussion.

Thanks,

Brent Baum DISC Library Assistant t: 472-4547 e: bbaum2@unlnotes.unl.edu w: cdrh.unl.edu

URL: cdrh.unl.edu

Originally submitted by: Todd Jensen

[tsteiner]

Submitted By: Timothy Steiner Adddate: 2011-09-15 12:52:20 Sounds like they might need to change the name of their tomcat server so that it doesn't conflict, and then we need to talk with neospire about setting up a reverse proxy to said server.

[tsteiner]

Submitted By: Keith Nickum Adddate: 2011-09-19 15:36:25 Technically the tomcat server is at libxml1a.unl.edu through port 8080, so there shouldn't be a conflict. I believe that should be the extent we need; if we can set up reverse proxies as needed, either through a ticket to neospire (?) or through some other method. I'm concerned about the "as needed" part though, we are always in the process of creating new projects, so while we could work a system that works, would it be onerous to continue doing in the future.

Another option I came up with would be to host the cdrh pages in the CMS from another site (cdrhhome.unl.edu) and then point cdrh.unl.edu to a server to reverse proxy the CMS content to cdrhhome.unl.edu and proxy cdrh.unl.edu/projects to whatever tomcat, etc. servers we'd like. That has the advantage of not needing to mess with any odd settings for the CMS and all users would still see cdrh.unl.edu, cdrh.unl.edu/projects (they just wouldn't realize the content was being proxied to them). Since we already have a number of reverse proxies, this should work well for us to maintain, and wouldn't require any weird changes that no one else on campus needs. Thoughts?

[tsteiner]

Originally Created By: bbieber2

I really dislike using reverse proxies to servers which are not under the same security models. This represents a risk for our project, and goes beyond what I would consider we do for generic sites on the CMS.

I would prefer the last option where they proxy the UNLCMS pages into a domain & server that they own.