AW: AW: AW: [squid-users] Troubleshooting squid: modified content

Jeff,

I screwed around on the debug_level variable, and found in cache.log the
following lines:

2009/05/04 11:58:39.891| WARNING: HTTP header contains NULL characters
{Server: 4D_v11_SQL/11.4.0
Date: Mon, 04 May 2009 09:58:39 GMT
Cache-Control: max-age=0, private, must-revalidate
Connection: close
Content-length: 365
Content-Type: text/xml
Expires: ue, 04 May 99 09:58:39 GMT}
2009/05/04 11:58:39.891| HttpMsg::parse: cannot parse isolated headers in
'HTTP/1.0 200 OK
 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Server: 4D_v11_SQL/11.4.0
Date: Mon, 04 May 2009 09:58:39 GMT
Cache-Control: max-age=0, private, must-revalidate
Connection: close
Content-length: 365
Content-Type: text/xml
Expires: ue, 04 May 99 09:58:39 GMT'
2009/05/04 11:58:39.891| processReplyHeader: Non-HTTP-compliant header:
'HTTP/1.0 200 OK
 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Server: 4D_v11_SQL/11.4.0
Date: Mon, 04 May 2009 09:58:39 GMT
Cache-Control: max-age=0, private, must-revalidate
Connection: close
Content-length: 365
Content-Type: text/xml
Expires: ue, 04 May 99 09:58:39 GMT'
2009/05/04 11:58:39.891| Unknown HTTP status code: 600
2009/05/04 11:58:39.891| InvokeHandlers: 4694974055C0D959D4D13969B82ED7E9
2009/05/04 11:58:39.891| StoreEntry::InvokeHandlers: checking client #0
2009/05/04 11:58:39.891| ctx: exit level 0
2009/05/04 11:58:39.891| fwdFail: ERR_INVALID_RESP "Bad Gateway"
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Do you believe that this is a server-side problem? A bad HTTP protocol
implementation on that particular server?

Unfortunatly, I cannot check if that also happens when trying to send tax
reports to the officials. I'll take a month until I have the next to
send....

  Peter

> -----Ursprüngliche Nachricht-----
> Von: Jeff Pang [mailto:pangj_at_arcor.de]
> Gesendet: Montag, 4. Mai 2009 11:25
> An: Sig Pam - ITServ GmbH
> Cc: squid-users_at_squid-cache.org
> Betreff: Re: AW: AW: [squid-users] Troubleshooting squid:
> modified content
>
> Sig Pam:
> > Jeff,
> >
> > Thanks again. I will get the source of Squid3.0-stable14
> and retry if that
> > solves my problem. That'll take a few days and envolves
> setting up a test
> > server, since I won't pollute my production proxy.
> >
>
> I'm sorry that I have made a mistake. I also didn't see the full page
> with Squid proxy.
> In last message I said "all goes fine" just mean I could see
> the page,
> but really coundn't see the "Knowledgebase" content in the table.
>
> There are also these messages in cache.log:
>
> 2009/05/04 17:17:22| ctx: exit level 0
> 2009/05/04 17:17:22| ctx: enter level 0:
> 'http://kb.4d.com/DAX/login?username=public&password='
> 2009/05/04 17:17:22| WARNING: HTTP header contains NULL characters
> {Server: 4D_v11_SQL/11.4.0
> Date: Mon, 04 May 2009 09:17:22 GMT
> Cache-Control: max-age=0, private, must-revalidate
> Connection: close
> Content-length: 365
> Content-Type: text/xml
> Expires: ue, 04 May 99 09:17:22 GMT}
>
>
> Shall Amos be helpful here? thanks.
>
> --
> Jeff Pang
> DingTong Technology
> www.dtonenetworks.com
>
>
Received on Mon May 04 2009 - 11:17:22 MDT