httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 45474] Reverse proxy and very first request = Invalid direct reference to form login page.
Date Thu, 24 Jul 2008 14:12:20 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=45474


Rob Stewart <rob.rstuff@googlemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




--- Comment #2 from Rob Stewart <rob.rstuff@googlemail.com>  2008-07-24 07:12:19 PST
---
'Sounds like' - hmmm.

I've logged the details in the user forum already and I'm more than willing to
take any suggestions on board for how I fix this, but I've tweaked
configurations and I've checked many documents and followed several. I've spent
the better part of a week trying to fix this issue with no luck.

The question thus becomes how could a configuration issue fail only once after
the server starts up and never again? What part of configuration would do that?

To me it 'sounds like' the HTTPD server is passing on the initial request to
the Tomcat servers incorrectly. I believe I've ruled out the issue being caused
by any browser, client and the Tomcat servers themselves, that leaves the HTTPD
server. (perhaps it's the proxy/proxy balancing module?)

There's only six modifications made in the attached httpd.conf file - and only
ONE relates to a reverse proxy...

<Proxy balancer://mycluster>
  BalancerMember ajp://127.0.0.1:18009
  BalancerMember ajp://127.0.0.1:28009
</Proxy>
ProxyPass /FakeServer   balancer://mycluster/FakeServer   lbmethod=bytraffic
stickysession=JSESSIONID|jsessionid
ProxyPass /FakeNAServer balancer://mycluster/FakeNAServer lbmethod=bytraffic
stickysession=JSESSIONID|jsessionid

6 lines - You can even take out the last line as that one doesn't have
authentication, NA = No Authentication.

I understand this isn't support, but I can't see where I've gone wrong, so I've
logged a bug. As I've said above, if it is a configuration problem why does it
only fail with the first request?


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message