[squid-users] Web app not working through proxy

Greetings All,

I ran into an issue today where a web application accessed over SSL was not
working through the proxy server. The users were able to log into the app
but then some functionality would not work within the application. Certain
fields would not appear in the web browser and then the web browser would
hang and would have to be killed. As soon as I bypassed the proxy, this web
app works fine.

I have added an exception for this website in the PAC file for the browser,
so the users are functioning as normal for now, but I would be appreciative
if anyone has any ideas of things I could do to allow these users to use the
proxy server for this connection.

Here are excerpts from access.log and cache.log. The systems is SuSE 8.0,
version 2.5.STABLE1-20030102.

Access.log:

1046117295.438 2306 10.10.14.154 TCP_MISS/200 20127 CONNECT
wires.theonenet.com:443 - DIRECT/159.53.238.222 -
1046117300.609 7583 10.10.14.154 TCP_MISS/200 32328 CONNECT
wires.theonenet.com:443 - DIRECT/159.53.238.222 -
1046117302.317 7161 10.10.14.154 TCP_MISS/200 12249 CONNECT
wires.theonenet.com:443 - DIRECT/159.53.238.222 -
1046117302.516 529 10.10.14.154 TCP_MISS/200 1625 CONNECT
wires.theonenet.com:443 - DIRECT/159.53.238.222 -
1046117308.507 4980 10.10.14.154 TCP_MISS/200 123549 CONNECT
wires.theonenet.com:443 - DIRECT/159.53.238.222 -
1046117316.859 8335 10.10.14.154 TCP_MISS/200 77734 CONNECT
wires.theonenet.com:443 - DIRECT/159.53.238.222 -
1046117346.836 29977 10.10.14.154 TCP_MISS/200 39 CONNECT
wires.theonenet.com:443 - DIRECT/159.53.238.222 -
1046117346.850 44355 10.10.14.154 TCP_MISS/200 39 CONNECT
wires.theonenet.com:443 - DIRECT/159.53.238.222 -
1046117346.850 46263 10.10.14.154 TCP_MISS/200 39 CONNECT
wires.theonenet.com:443 - DIRECT/159.53.238.222 -
1046117346.850 44555 10.10.14.154 TCP_MISS/200 39 CONNECT
wires.theonenet.com:443 - DIRECT/159.53.238.222 -

Cache.log

2003/02/24 09:12:26| Ready to serve requests.
2003/02/24 11:42:57| parseHttpRequest: Requestheader contains NULL
characters
2003/02/24 11:42:57| clientReadRequest: FD 115 Invalid Request
2003/02/24 11:42:57| parseHttpRequest: Requestheader contains NULL
characters
2003/02/24 11:42:57| clientReadRequest: FD 131 Invalid Request
2003/02/24 12:44:09| sslReadServer: FD 118: read failure: (104) Connection
reset by peer
2003/02/24 12:44:09| sslReadServer: FD 118: read failure: (104) Connection
reset by peer
2003/02/24 13:13:31| sslWriteClient: FD 69: write failure: (104) Connection
reset by peer.
2003/02/24 13:17:48| sslReadServer: FD 73: read failure: (104) Connection
reset by peer
2003/02/24 13:17:48| sslReadServer: FD 83: read failure: (104) Connection
reset by peer
2003/02/24 13:17:48| sslReadServer: FD 94: read failure: (104) Connection
reset by peer

Thanks.

Grant Sturgis
This electronic message transmission is a PRIVATE communication which
contains information which may be confidential or privileged. The
information is intended to be for the use of the individual or entity named
above. If you are not the intended recipient, please be aware that any
disclosure, copying, distribution or use of the contents of this information
is prohibited. Please notify the sender of the delivery error by replying to
this message, or notify us by telephone (877-633-2436, ext. 0), and then
delete it from your system.
Received on Mon Feb 24 2003 - 13:32:52 MST