Hello
I'm trying to get Fossil to work with CGI using Hiawatha webserver. I'm
using the following CGI script:
#!/usr/bin/fossil
repository: /var/www/fossil/test.fossil
When I access it /fossil.cgi I, my browser now says it is at
/fossil.cgi/index and I get an 404.
The following test cgi
On Sat, Nov 20, 2010 at 7:36 AM, Richard Hipp d...@sqlite.org wrote:
2010/11/20 Søren Enevoldsen senevoldse...@gmail.com
Hello
I'm trying to get Fossil to work with CGI using Hiawatha webserver. I'm
using the following CGI script:
#!/usr/bin/fossil
repository:
The output I get is:
--
Hello world wide web.
DOCUMENT_ROOT=/var/www/html
GATEWAY_INTERFACE=CGI/1.1
HTTPS=off
HTTP_ACCEPT=text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
HTTP_ACCEPT_CHARSET=ISO-8859-1,utf-8;q=0.7,*;q=0.7
I'm browsing it on a computer running Windows, the server is Linux.
Maybe Firefox decides that the line-feed should be preceeded by a
carriage return? Not that it matter for this script.
Stephan Beal wrote:
2010/11/20 Søren Enevoldsen senevoldse...@gmail.com
mailto:senevoldse...@gmail.com
Thank you very much for your help.
It was indeed not configured correctly. An option, EnablePathInfo was
disabled by default. Enabling it seems to have solved.
Richard Hipp wrote:
2010/11/20 Søren Enevoldsen senevoldse...@gmail.com
mailto:senevoldse...@gmail.com
From
The developer of Hiawatha suggested that using URL rewriting might be a
better method than PATH_INFO. What is your thoughts on that?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On 11/20/2010 11:01 AM, Søren Enevoldsen wrote:
The developer of Hiawatha suggested that using URL rewriting might be a
better method than PATH_INFO. What is your thoughts on that?
PATH_INFO is a very, very common requirement for CGI programs. In Apache
and Lighttpd (at least) it 'just works'.
7 matches
Mail list logo