Your patch has been applied.  Thanks for tracking this down.

Please note that none of the developers use nginx, so this kind of bug
tends to go unnoticed if unreported.  So please do speak up when you see
problems.


On Fri, Mar 21, 2014 at 11:08 PM, Joseph Prostko <joe.pros...@gmail.com>wrote:

> Hello,
>
> I am running Nginx 1.5.12, and noticed that Fossil 1.28 fails to work
> when set up to run via SCGI.  SCGI works fine with Fossil 1.27, and
> after doing a binary search, I concluded definitively that 63a84cb66e
> from 2014-10-17 is the culprit.
>
> To be extra thorough, I tried Nginx 1.0.15, 1.2.9, 1.4.7, and 1.5.12,
> and they all exhibit this behavior.  All versions of Fossil and Nginx
> were built from source to aid the speed of my binary searching.
>
> To fix the issue on my end, I simply did the following change to
> 9b7298b74f of Fossil on line 879 of src/cgi.c:
>
> - const char *zPathInfo = cgi_parameter("PATH_INFO","");
> + const char *zPathInfo = cgi_parameter("PATH_INFO",0);
>
> Essentially this reverted to the code that was present before 63a84cb66e.
>
> After rebuilding with that change, Fossil worked again via SCGI on
> Nginx as expected.
>
> I will file a ticket about this, but as instructed in the bug tracker,
> I opened a discussion here first.
>
> Also, this behavior was previously discussed in the mailing list post
> below by Jon.  I had the exact same problem he was describing in the
> thread before I narrowed down what the issue was.
>
>
> https://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg14823.html
>
> - joe
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>



-- 
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

Reply via email to