Re: [squid-users] Re: "Origin" header fails on bridged-tproxy squid

Origin is relatively new;
  http://tools.ietf.org/html/draft-ietf-websec-origin-00

In a nutshell, it's sort of like a referer just for the authority part of the URL (i.e., it omits the path).

Robert -- what exactly is breaking? Is your tproxy stripping any headers or modifying the request URL? Is there anything else unusual about your setup?

Cheers,

On 27/02/2011, at 4:08 PM, Amos Jeffries wrote:

> On 26/02/11 13:19, Robert Pipca wrote:
>> Sorry,
>>
>> The correct site to see the problem is:
>>
>> http://vistoria.brochweld.com.br/bvsweb/paginas/tela_login.aspx
>>
>
> There is no such header as "Origin:" in HTTP. Did you means "Host:" ?
>
> Squid uses the Host: header to determine destination IP unless
> configured otherwise. What are you seeing as the problem?
>
>
> Amos
> --
> Please be using
> Current Stable Squid 2.7.STABLE9 or 3.1.11
> Beta testers wanted for 3.2.0.5

--
Mark Nottingham       mnot_at_yahoo-inc.com