On 8/29/16, John Found <johnfo...@asm32.info> wrote: > I am running fossil in cgi mode on an experimental web server. The web > server supports only FastCGI interface, so the fossil is spawned using > "fcgiwrap" tool. Anyway, we are hunting for a problem. > > When requesting the main page "/fossil/repo/name/", fossil returns 302 and > redirects to "/fossil/repo/name/index". > The 302 response, contains some message body "Moved" which is ignored by the > browser. > > But if the request contains the header "Accept-Encoding: gzip", the response > contains the header "Content-Encoding: gzip" and > it seems that fossil compresses the response body. Is this the case, or the > mess happens somewhere else.
Yes, Fossil compresses the reply in CGI mode. > IMHO, the cgi script should not return "Content-Encoding" header, because > this is the function of the web server. > I have never before encountered that opinion. It would be a problem for me, because my bespoke webserver used on the www.fossil-scm.org website does NOT attempt to compress CGI content. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
