Hi there. I am currently responsible for a reasonably large cms
(http://www.hio.no). Now, the problem is, my predecessor has *not*
implemented a cache for this site, and the server is getting loaded down
quite heavily due to many mysql-requests.
Enter varnish (1.0.2-7 on Red Hat AS4) but,
On Jan 17, 2007, at 09:08, Kenneth Rørvik wrote:
Hi there. I am currently responsible for a reasonably large cms
(http://www.hio.no). Now, the problem is, my predecessor has *not*
implemented a cache for this site, and the server is getting loaded
down quite heavily due to many mysql-reque
Eirik Øverby wrote:
I'm not going to solve your problem here, but I have a question: Why are
you using a permanent redirect here?? It is, from my understanding, not
at all a permanent redirect, it's a conditional one -- and you have no
intention to blocking access to the / page from internal u
Kenneth Rørvik wrote:
Now, provided I get the right test in place - the next question is how
to handle the redirect itself. You could either send the request on to
Looks like the test is OK now. Next problem: piping to the server now
makes it impossible for the server to distinguish clients
How can I have varnish itself send a http 301 or 307 to the client with
the correct URL? Cannot find this documented, or on google for that matter.
Hmm, a bit quick:
http://projects.linpro.no/pipermail/varnish-misc/2006-October/000104.html
Any thoughts on when this can be expected?
--
Kenneth
Kenneth Rørvik <[EMAIL PROTECTED]> writes:
> Kenneth Rørvik wrote:
>
>> Now, provided I get the right test in place - the next question is
>> how to handle the redirect itself. You could either send the request
>> on to
>
> Looks like the test is OK now. Next problem: piping to the server now
> m
