[Gllug] Dishonouring Redirects

Steve Nelson sanelson at gmail.com
Mon May 23 18:35:10 UTC 2005


On 5/23/05, Anthony Newman <anthony.newman at uk.clara.net> wrote:
> 301 is a response code, which has nothing to do with requests. The HTTP
> user agent (i.e. browser etc.) is responsible for acting on the
> 301+Location response, generally by creating a fresh request.

Yes - I thought this after I first posted.  The browser establishes
the connection, and the server knows nothing about the machine which
gave the browser the redirect.

> What is the Referer header set to for the redirected request which
> arrives at 164.109.84.143:80? 

I'll have a look in the logs.


> This cannot be relied upon strictly
> speaking, but most browsers produce accurate Referers AFAIK, which may
> allow you to determine a "bounced" request.
> I can see what else you might have meant, but I won't elaborate. More
> info about the situation and your proposed solution might be useful...

Well the solution is that I've said there's nothing I can do about it,
and our Korean 'squatter' is not doing anything illegal.  That Nestle
should write to Danone and let them know what's happening, and say
that its not of their doing, nor do they approve of it.

I just wondered if there was some way of seeing the information I say
in the packet I pasted, and doing some kind of intelligent filtering
based on the content of that packet.

> Ant

S.
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug




More information about the GLLUG mailing list