On Fri, Mar 28, 2008 at 4:58 AM, Florian Engelhardt <[EMAIL PROTECTED]>
wrote:
> You could store the sessions on a separate server, for instance on a
> memcache or in a database
Good idea. (Though if you use memcached, you'd probably want to
periodically copy the backing store to a file to surv
On Fri, 28 Mar 2008 12:05:23 +0100
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> I got a question regarding the Directors in varnish vcl.
> If user A is logging in to http://mywebsite.com and the website is
> using varnish (with directors) in front of 4 backend servers. The 4
> backend servers is identic
On 2008-3-28 19:05, [EMAIL PROTECTED] wrote:
> Hi,
>
> I got a question regarding the Directors in varnish vcl.
> If user A is logging in to http://mywebsite.com and the website is using
> varnish (with directors) in front of 4 backend servers.
> The 4 backend servers is identical.
>
> User A
Hi,
I got a question regarding the Directors in varnish vcl.
If user A is logging in to http://mywebsite.com and the website is using
varnish (with directors) in front of 4 backend servers.
The 4 backend servers is identical.
User A is logging in and hits server 1. He then goes to his profile
Hi,
I have some questions about "varnishncsa". I would like to split access
log via "varnishncsa" by Host header because the backend uses naming
virtual hosts.
I tried "varnishncsa -i RxHeader -I 'Host: mydomain'" but nothing
display on screen. Even "varnishncsa -I RxHeader" can not show any log
On Fri, 28 Mar 2008 10:50:45 +0100
Florian Engelhardt <[EMAIL PROTECTED]> wrote:
> Hello,
>
> i have a question about access loggin in varnish. On the "old"
> environment we had just a plain lighttpd on port 80 an its logfile.
> When caching via varnish in the "new" environment, most of the
> req
Hello,
i have a question about access loggin in varnish. On the "old"
environment we had just a plain lighttpd on port 80 an its logfile.
When caching via varnish in the "new" environment, most of the requests
will not hit lighttpd and will therefor not show up in its access.log
file. Is there any
On Fri, 28 Mar 2008 10:41:43 +0100
Stig Sandbeck Mathisen <[EMAIL PROTECTED]> wrote:
> On Fri, 28 Mar 2008 08:15:59 +0100, Florian Engelhardt
> <[EMAIL PROTECTED]> said:
>
> Received from backend.
>
> >15 RxHeader b X-JSON: foobar
>
> Varnish object contains the header.
>
> >14 Obj
On Fri, 28 Mar 2008 08:15:59 +0100, Florian Engelhardt <[EMAIL PROTECTED]> said:
Received from backend.
>15 RxHeader b X-JSON: foobar
Varnish object contains the header.
>14 ObjHeaderc X-JSON: foobar
Sent to client.
>14 TxHeader c X-JSON: foobar
Lost on the way :P
>
On Mar 27, 2008, at 10:35 PM, Stig Sandbeck Mathisen wrote:
> 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 authenti
On Fri, 28 Mar 2008 06:27:22 +0100
Stig Sandbeck Mathisen <[EMAIL PROTECTED]> wrote:
> 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 wh
11 matches
Mail list logo