Hello,
i've got a problem with the X-JSON HTTP-Header not beeing delivered by
varnish in pipe and pass mode.
My application runs on PHP with lighttpd, when querying the lighty
direct (via port :81), the header is present in the request. PHP Script
is as follows:
?php
header('X-JSON: foobar');
The Transfer-Encoding: header is missing from the Varnish response as well.
--Michael
On Thu, Mar 27, 2008 at 7:55 AM, Florian Engelhardt [EMAIL PROTECTED]
wrote:
Hello,
i've got a problem with the X-JSON HTTP-Header not beeing delivered by
varnish in pipe and pass mode.
My application
In the default vcl, we have the following test...
if (req.http.Authenticate || req.http.Cookie) {
pass;
}
What issues an Authenticate header? Was this supposed to be
Authorization?
Ric
___
On Mar 27, 2008, at 5:50 PM, Cherife Li wrote:
On 03/28/08 06:47, Ricardo Newbery wrote:
In the default vcl, we have the following test...
if (req.http.Authenticate || req.http.Cookie) {
pass;
}
What issues an Authenticate header? Was this
On Thu, 27 Mar 2008 15:55:09 +0100, Florian Engelhardt [EMAIL PROTECTED] said:
Why is this X-JSON header missing when requested via varnish?
It would help if you include output from varnishlog which shows both
the client and the backend communication from one request. That'll
provide
On Thu, 27 Mar 2008 15:47:00 -0700, Ricardo Newbery [EMAIL PROTECTED] said:
What issues an Authenticate header? Was this supposed to be
Authorization?
Maybe, not sure.
However, in order to check for HTTP authenticated connections, the
headers look something like:
GET / HTTP/1.1
Host:
On Fri, 28 Mar 2008 08:50:41 +0800, Cherife Li [EMAIL PROTECTED] said:
I'm also wondering that whether this http.Authenticate means
Proxy-Authenticate , Proxy-Authorization, and WWW-Authenticate
headers defined in RFC 2616.
req.http.Authenticate would refer to a single request http header
