Thank you for the clarification, Geoff!
I've traced this missing cookie header issue down to a very strange
problem: it seems to be a timing issue somehow. If I put a usleep(1)
in our code at the start of our perl Response filter, the cookies are
no longer missing for each response. For that ma
> Client-Transfer-Encoding: chunked <-- **missing from below**
> Content-Length: 123434 <-- **missing from above**
you don't need a Content-Length header of your client uses a chunked
transfer encoding, so these two are kinda mutually exclusive.
fortunately, you also don't need to know that -
Yup, I'm directly hitting the application, there's nothing in between
my client and the server.
On Dec 19, 2007 1:39 PM, Torsten Foertsch <[EMAIL PROTECTED]> wrote:
> On Wed 19 Dec 2007, Adam Woodworth wrote:
> > Content-Length: 123434 <-- **missing from above**
>
> Are you really sure you hit yo
On Wed 19 Dec 2007, Adam Woodworth wrote:
> Content-Length: 123434 <-- **missing from above**
Are you really sure you hit your application in these cases? If you don't set
the Content-Length header. Maybe a cache in between does.
Torsten
Hi,
I'm using a web stack consisting of Apache 2.2.6, mod_perl 2.0.3, and
libapreq 2.10 (from their svn branch), and I'm seeing a problem where
some headers are sometimes missing from the HTTP response.
Specifically, we are setting a couple cookies from our mod_perl
application, and about half th
