topic Re: invalid xml or is not responding in Operating System - Linux

invalid xml or is not responding

'chris' — Thu, 05 Feb 2009 18:14:52 GMT

hi

We have proxy squid/3.0.PRE5 installed on linux debian etch stable and we have big problems with one very important webseite.

We're getting quite often this error message in browser:

invalid xml or is not responding

We don't know howto find and fix this problem?
Is it the problem of the timeout?
Knows someone more about this error message?

Which squid log should show this problem ?

Re: invalid xml or is not responding

Ivan Ferreira — Thu, 05 Feb 2009 19:19:53 GMT

Maybe, to start diagnosing the problem, you can use the no_cache option to avoid caching of that site.

See:

http://www.geocities.com/vladislav_isaev/squid/FAQ-7.html

Maybe the problem is at origin.

Re: invalid xml or is not responding

'chris' — Tue, 10 Feb 2009 01:40:41 GMT

thx, I'll try but In Squid 3 no_cache is changed to cache

http://www.squid-cache.org/Versions/v3/3.0/cfgman/cache.html

so:

cache deny ACL

is correct.

Re: invalid xml or is not responding

'chris' — Thu, 12 Feb 2009 19:22:35 GMT

I tried:

acl mydomain dstdomain .mydomain.net
cache deny mydomain

but it doesn't help.

the remote webserver uses a kind of balancing system and uses asp
the user is logging into and getting an asp ID in the header.
this session should stay of the same, one of this balancing server.
the problem is, over squid the user gets second asp ID, is not staying
on the same server, switching to the other one and getting this error above.

without proxy works well.

Re: invalid xml or is not responding

Ivan Ferreira — Thu, 12 Feb 2009 20:28:13 GMT

I think I don't understand correctly the problem, but if you are using IDs, then you should be accesing via https, and https connections should not be cached/proxied.

Â¿Are you using https?

Re: invalid xml or is not responding

'chris' — Thu, 12 Feb 2009 20:39:59 GMT

no, it's only HTTP with a header ID

Re: invalid xml or is not responding

Ivan Ferreira — Thu, 12 Feb 2009 20:57:04 GMT

Check this link, it discusses how squid handles dynamic pages and the differences between 2 and 3. It may help you:

http://wiki.squid-cache.org/ConfigExamples/DynamicContent

Re: invalid xml or is not responding

'chris' — Thu, 12 Feb 2009 21:36:08 GMT

thx, but this is not cgi-bin, just asp

howto configure squid 3 to deny cache of all asp websites ?

Re: invalid xml or is not responding

Ivan Ferreira — Thu, 12 Feb 2009 21:49:20 GMT

That is just a sample, and it's a regex, cgi-bin and the ? symbol are by default, you can include for example "asp" in that rule to match asp pages, there should be a common pattern in the URL of your asp pages, like .asp.

Re: invalid xml or is not responding

'chris' — Thu, 12 Feb 2009 22:43:14 GMT

you mean like this?

hierarchy_stoplist asp ?
acl QUERY urlpath_regex asp \?
cache deny QUERY

Re: invalid xml or is not responding

Ivan Ferreira — Fri, 13 Feb 2009 11:57:09 GMT

Yes, if in your URL the word asp appears somewhere.

Re: invalid xml or is not responding

'chris' — Fri, 13 Feb 2009 12:04:49 GMT

thx, but what about:

acl asp url_regex .asp
cache deny asp

Re: invalid xml or is not responding

Ivan Ferreira — Fri, 13 Feb 2009 13:12:39 GMT

That should also work, but in regular expressions, the "dot" just means "any" character. Then you should use \.asp.

Re: invalid xml or is not responding

'chris' — Fri, 13 Feb 2009 13:20:11 GMT

thx again, but is it a good idea to put both of them in squid.conf?

acl asp url_regex \.asp
cache deny asp

hierarchy_stoplist asp ?
acl QUERY urlpath_regex asp \?
cache deny QUERY

Re: invalid xml or is not responding

Ivan Ferreira — Fri, 13 Feb 2009 13:50:12 GMT

>> thx again, but is it a good idea to put both of them in squid.conf?

No, just ose one of them, like:

hierarchy_stoplist \.asp ?
acl QUERY urlpath_regex \.asp \?
cache deny QUERY

Re: invalid xml or is not responding

'chris' — Sun, 15 Feb 2009 02:04:18 GMT

thx a lot !

but I I've read somewhere, that hierarchy_stoplist is NOT related to caching, only forwarding.

'cache deny' for example is the equivalent directive affecting caching.

greetings
chris