al Message-
From: Qingshan Xie [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 06, 2006 12:36 AM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] issue on 304 return code
Thx a lot Joshua for your quick reply.
We did some debugging. SiteMinder indeed returned all SiteMinder headers(
C
On 7/5/06, Qingshan Xie <[EMAIL PROTECTED]> wrote:
Thx a lot Joshua for your quick reply.
We did some debugging. SiteMinder indeed returned all
SiteMinder headers( Cookies and SessionID), but some
how Apache in the front stripped them off and return
304. We did not implement cache, I don't know
Thx a lot Joshua for your quick reply.
We did some debugging. SiteMinder indeed returned all
SiteMinder headers( Cookies and SessionID), but some
how Apache in the front stripped them off and return
304. We did not implement cache, I don't know why it
has if-modify-since in the header and retur
On 7/5/06, Qingshan Xie <[EMAIL PROTECTED]> wrote:
Thanks Joshua.
We are using SiteMinder for
Authentication/Authorization, and Single-Sign-On. The
missing part of the headers is SiteMinder SessionID
and Cookies, which causes the Single-Sign-On failed.
Is there any way to append those headers
Thanks Joshua.
We are using SiteMinder for
Authentication/Authorization, and Single-Sign-On. The
missing part of the headers is SiteMinder SessionID
and Cookies, which causes the Single-Sign-On failed.
Is there any way to append those headers back when
Apache throws 304? Can we use mod_head
On 6/29/06, Qingshan Xie <[EMAIL PROTECTED]> wrote:
Hi,
We have an Apache-2.0.54 in front and an WebSphere
in backend. Whenever Apache threw 304 return code. A
lot of info in the header was stripped away. Is there
any a way to keep all those header information when
got 304?
Which headers
