On 9/11/2010 9:58 AM, Rainer Jung wrote: > On 11.09.2010 04:12, Mike Schleif wrote: >> >> On 9/10/2010 3:19 PM, Mike Schleif wrote: >> > >> > On 9/10/2010 12:07 PM, Sander Temme wrote: >> > > >> > > On Sep 10, 2010, at 5:23 AM, Mike Schleif wrote: >> > > >> > >> SSL: move all SSL to the new frontend? No SSL running on legacy web >> > server? >> > > >> > > Absolutely. You'll find that Apache 2.2.16 comes with mod_ssl >> > bundled. Terminate SSL on the currently shipping server. >> > > >> > > Note that the Apache Software Foundation only ships source code: an >> > important distinction on a platform that doesn't bundle the web server >> > by default, and where users usually don't wield compilers. However, a >> > build with and without SSL enabled is usually made available as a >> > courtesy, and can be downloaded from>> > http://httpd.apache.org/download.cgi . You may also find Windows builds
>> > on sites like http://www.apachelounge.com/ . >> > > >> > > S. >> > >> > Is there more to it than ProxyPass and ProxyPassReverse ? >> > >> > I found this: >> > >> > http://www.apachetutor.org/admin/reverseproxies >> >>> > I want this to work as simply as possible. I know that SSL moves to the
>> > NEW server. Which modules need I load? According to the above link, I >> > think we need these: >> > >> > ### MUST have for Reverse Proxy >> > LoadModule proxy_module modules/mod_proxy.so >> > LoadModule proxy_http_module modules/mod_proxy_http.so >> > LoadModule headers_module modules/mod_headers.so >> > LoadModule deflate_module modules/mod_deflate.so >> > ### >> > >> > However, that link also mentions the following, which I do not find in >> > the httpd.conf: >> > >> > LoadFile /usr/lib/libxml2.so >> > LoadModule xml2enc_module modules/mod_xml2enc.so >> > LoadModule proxy_html_module modules/mod_proxy_html.so >> > >> > >> > Please, advise. Thank you. >>>> Still not certain whether or not we need the XML and HTML modules. Do we?
> > You don't need it in general. mod_proxy_html allows very powerful > rewriting of e.g. links contained in the responses returned from the > backend server. If the backend includes self-referential absolute links > and you have to rewrite them to point to the proxy instead (fifferent > name or different port), mod_proxy_html is very useful. > > As long as the wrong URLs only occur in redirects, a simple > ProxyPassReverse suffices. If you only want to replace very simple > patterns in the content of the responses, mod_substitute might do, which > is nowadays bundled with Apache 2.2.x. > > Regards, > > RainerOK, thank you, the Apache community, for helping me overcome the Reverse Proxy and SSL issues. Most of this works now.
We have two (2) remaining issues:[1] Most of the HTML served by the legacy Apache server Reverse Proxies successfully. One example that DOES NOT follows:
Does NOT work: <a href=".\VENDWEB_201_vi_3M_0.pdf"> DOES work: <a href="VENDWEB_201_vi_3M_0.pdf">Actually, the former works with IE, but does NOT work with Firefox. Editing the former to the latter, the latter works with both IE and Firefox.
Is this the type of problem that the HTML and/or XML modules will resolve? Is this automatic? Or, dependent on configuration of modules?
[2] There is another problem with a form that will NOT accept entries into form fields. Still trying to identify the source to the problem; but, again, this form DOES work with IE, and does NOT work with Firefox. I'm hoping that the source is similar to [1] above.
What need I look into? Resolving these issues, my client is ready to Reverse Proxy in Production; and their problem is resolved. Thank you, for all of your attention to this.
If ever I can be of service to you; contact me at once. I wish for you a truly extraordinary day ... -- Best Regards, Mike Schleif 612-235-6060 http://mdsresource.net http://www.linkedin.com/in/schleif http://facebook.com/MDSResource http://twitter.com/mikeschleif --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|