On 23/07/18 01:29, Andrea Venturoli wrote: > Hello. > > I'm maintaining several installations on FreeBSD and I've been notified > a specific web application is not working anymore after the upgrade. > > > > Accessing this app with FireFox and Squid 3.5.27, it works correctly. > > Doing the same after the upgrade to 4.1 lets the user arrive up to a > point and then get a "Loading" message which will never go away. > > > > Using FireFox network debugger, I see a couple of 400 error and in fact, > if I try to open those URL I get: > >> Invalid Request error was encountered while trying to process the >> request: >> >> Some possible problems are: >> >> Missing or unknown request method. >> >> Missing HTTP Identifier (HTTP/1.0). >> >> Request is too large. >> >> Content-Length missing for POST or PUT requests. >> >> Illegal character in hostname; underscores are not allowed. >> >> HTTP/1.1 "Expect:" feature is being asked from an HTTP/1.0 software. > > > > The above error is not quite informative (too broad) There are a lot of things that can be wrong about requests sent. One of them did. That list is not comprehensive either, just the things which can be easily checked by users/admin without access to the proxy. FYI: The template delivered has inline javascript for hiding the messages that are irrelevant to this particular request. If you open the URL in the browser (not debugging) it should reduce down to the ones which are relevant. You could also look at the debugger info abut the request message sent and compare those values yourself. > and there's nothing > useful in the logs. > > Here are those two URL (which unfortunately I have to partially obfuscate): > >> http://xxxxxxxxxxx.xxxxxxxxxxx.xx/rest?method=navi_path.add&opera=I029&tipo=0&descr=XXXXXXXXX%20-%20Xxxxxxx%20xxxxxxxxxxx%20xxx%2030/12/2014%20-%20XXXX&xxxxx_xxxx=0¶ms={idDoc:%27C0002019%27,clasDoc:%27XXXXXX%27,nomeDoc:%27XXXXXXXXX%20-%20Xxxxxxx%20xxxxxxxxxxx%20xxx%2030/12/2014%20-%20XXXX%27,_X_TRACK_ID:%xxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx%27}&_ts=1532264445584&_dc=1532264445584 >> > >> http://xxxxxxxxxxx.xxxxxxxxxxx.xx/php/ajax/openDocumentREST.php?core=xxxxxxxXXXX&query={%22field%22:%22id%22,%22mode%22:%22EQUAL%22,%22value%22:%xxxxxxxxxx_XXXXXXXXX%22}&nomeTab=&arts=&toHighlight=&XXXXXXXX=I029 >> > > (the x and X are always alphanumeric characters). > That is not very helpful info. If anyone here is going to use it we need the actual full URL to run tests on ourselves. > > I'm seeking help on how to better diagnose this: how can I find what > Squid 4 does not like in those URLs? > see above for initial things to check on. For more details in cache.log configure: debug_options ALL,1 11,4 25,5, 33,5 This is best done on a test proxy where you don't have a flood of other traffic happening in parallel. > None of the above causes seems to apply, IMVHO. > > Has some default changed from 3.5 to 4.1 which might trigger this problem? > There is increased HTTP compliance, checking and handling. The things which are configurable are all listed in the release notes AFAIK. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
