Re: [squid-users] Problem with intercept squid and boinc

I have visited the troubled URL in Firefox:

http://setiboincdata.ssl.berkeley.edu/sah_cgi/file_upload_handler

And it seems to look at the user-agent and output a speciall
message if your're using a web browser.

Maybe squid is changing some headers that setiboinc needs ...

WIll do some more test

Tks
Oliver

Henrik Nordstrom wrote:
> ons 2006-02-22 klockan 10:16 -0300 skrev Oliver Schulze L.:
>
>
>> and in the problematic squid server I see:
>> 1140566460.404 2060 192.168.2.90 TCP_MISS/100 123 POST
>> http://setiboincdata.ssl.berkeley.edu/sah_cgi/file_upload_handler -
>> DIRECT/66.28.250.125 -
>>
>> What does TCP_MISS/100 mean? As I see, the correct value should be
>> TCP_MISS/200
>>
>
> Correct. You should never see a 100 response code in Squid. This
> indicates there is something upstream which malfunctions and sends a 100
> Continue to your Squid even if the HTTP standard forbids this. Squid is
> HTTP/1.0, and 100 Continue requires HTTP/1.1.
>
> Something upstream ranges from
>
> Parent proxy
> Another intercepting proxy
> The origin server
>
> Regards
> Henrik
>

-- 
Oliver Schulze L.
<oliver@samera.com.py>