On Fri, Jan 30, 2009 at 5:04 PM, Carl Fyffe <carl.fyffe@xxxxxxxxx> wrote: > We have successfully configured our system to load balance across > multiple servers. We started out with: > > Users --> HTTPS --> Apache --> HTTP --> Glassfish > > This worked well, until we tried one of our scenarios where we > Post/Redirect/Get (PRG). This worked exactly as it was supposed to, > the url was exactly correct except the protocol was sending back HTTP > instead of HTTPS as expected. HTTP is blocked on the Glassfish servers > so the traffic was not getting through. To fix the problem we did > this: > > Users --> HTTPS --> Apache --> HTTPS --> Glassfish > > This solves the issue but the performance is degraded and > configuration is more complicated. Is it possible to not use HTTPS > between Apache and Glassfish? > > Is this a Glassfish issue or an Apache config issue? Is there > something obvious that I am missing? What you need to do is make sure your redirect (which I asume your Glassfish server generates) gets rewritten from http to https by the apache server (with ProcyPassReverse). Alternatively you can look if you can make the Glassfish server think it is a https server (so it servers https links back) without actually making it https. If for example your Glassfish has a configurable "base URL" you could set it to something "https://mywebsite.org";, asuming that this is how your site looks like from the outside. Krist -- krist.vanbesien@xxxxxxxxx krist@xxxxxxxxxxxxx Bremgarten b. Bern, Switzerland -- A: It reverses the normal flow of conversation. Q: What's wrong with top-posting? A: Top-posting. Q: What's the biggest scourge on plain text email discussions? --------------------------------------------------------------------- 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
|