DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40492>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40492


[EMAIL PROTECTED] changed:

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




------- Additional Comments From [EMAIL PROTECTED]  2006-09-14 14:11 -------

As much as you would like to see this as a duplicate of another problem
in mod_proxy I do not think it is simply that, because this case of lost
Set-Cookie headers only affects SSL connections.
When the connections are proxied over plain text connections the cookies
are not lost.
If this is really a problem in mod_proxy, it has to be aware of whether
the encapsulation used is plain text or SSL and treat these two alternatives
differently. That again makes no sense. Why should mod_proxy care about
the encapsulation?

If you have an explanation about how and why would mod_proxy destroy only
those Set-Cookie headers which are passed over SSL I will agree. Otherwise
I maintain that these are two different issues.

Secondly, if this really is a known problem with known patches available,
why are those patches not imported to the head of 2.0 branch?
I my eyes this would warrant releasing a new version 2.0.60 or something.

Using 2.2 is out of the question, because the authentication is done using
SiteMinder SSO tools. SiteMinder only supports 1.3.33 and higher or 2.0.54
and higher.
Going over to 2.2 breaks the module ABI, which means there is no SiteMinder
module for it.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to