Re: [fossil-users] Fossil SCGI Server Regression (from 1.36 to 1.37)

So I did bisect yesterday and oh wonder, everything worked properly. I don't know why I had an issue on Sunday but today it works on a new test server as well as on my production server. So all-clear for the server --scgi command. I would like to use the occasion to thank you developers of fossil

Re: [fossil-users] Fossil SCGI Server Regression (from 1.36 to 1.37)

2017-02-13 0:28 GMT+01:00 Richard Hipp : >> I guess there was a regression introduced somewhere between [8b03934e] >> and [fb4b87d9]. > > Would you be willing to bisect for us? Sure. I will report my findings later today. ___

Re: [fossil-users] Fossil SCGI Server Regression (from 1.36 to 1.37)

On 2/12/17, Thomas Bilk wrote: > > I guess there was a regression introduced somewhere between [8b03934e] > and [fb4b87d9]. Would you be willing to bisect for us? -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list

[fossil-users] Fossil SCGI Server Regression (from 1.36 to 1.37)

Hi all. I was finally upgrading my fossil server and encountered what I assume to be a regression. I am using the fossil server with scgi behind an nginx web server. I am hosting a directory with fossil repositories. These is my configuration: The fossil server is started with this fossil server