Dr. Richard Hipp, on Monday, April 29, 2019 09:18 AM, wrote...
> On 4/29/19, Jose Isaias Cabrera wrote:
> >
> > I know I can probably use cygwin to run this tool, but plain Windows is not
> > an option, right?
> >
>
> Althttpd is built around fork(). Windows does not support fork().
>
> A middle ground is Docker for Windows. I hesitate to speculate on its speed
> compared to the other three, but I think there’s reason to hope it could be a
> good option.
I would expect that running a Linux image inside Microsoft's hypervisor
environment and running a Linux image in
> On Apr 29, 2019, at 7:18 AM, Richard Hipp wrote:
>
> On 4/29/19, Jose Isaias Cabrera wrote:
>>
>> I know I can probably use cygwin to run this tool, but plain Windows is not
>> an option, right?
>>
>
> Althttpd is built around fork(). Windows does not support fork().
> The cygwin
Thanks, Dr. Hipp.
Dr. Richard Hipp, on Monday, April 29, 2019 09:18 AM wrote...
On 4/29/19, Jose Isaias Cabrera wrote:
>
> I know I can probably use cygwin to run this tool, but plain Windows is not
> an option, right?
>
Althttpd is built around fork(). Windows does not support fork().
The
On 4/29/19, Jose Isaias Cabrera wrote:
>
> I know I can probably use cygwin to run this tool, but plain Windows is not
> an option, right?
>
Althttpd is built around fork(). Windows does not support fork().
The cygwin implementation of fork() is convoluted, and I suspect slow,
though I have not
I know I can probably use cygwin to run this tool, but plain Windows is not an
option, right?
Richard Hipp, on Saturday, April 27, 2019 04:49 PM wrote...
On 4/27/19, Jungle Boogie wrote:
>
> Would you ever consider adding support to list an index of a directory?
> http://127.0.0.1/files would
> -SNIP-
>
> You do actually have to have the name of the CGI script in there.
> Otherwise, althttpd has know way of knowing what script to run.
>
Thanks for the explanations, comprehend all.
> >
> > Test #5:
> > Browser URL: http://127.0.0.1:8080/home/index.cgi/some/extra/path/info/
> >
On 4/27/19, Jungle Boogie wrote:
>
> Would you ever consider adding support to list an index of a directory?
> http://127.0.0.1/files would display whatever is in the /files directory.
Probably not. That seems to violate the keep-it-simple principle of
althttpd. On the rare occasions where a
On Sat 27 Apr 2019 7:44 AM, Richard Hipp wrote:
On 4/26/19, Carl Chave wrote:
Should "index.cgi" from line number 1923 in subject check in include a
leading forward slash? My index.cgi scripts aren't being found with
this version (or any subsequent version) unless I explicitly include
it as
On 4/27/19, Carl Chave wrote:
>> Fixed.
>
> Thanks!
>
>> Now with two users, maybe it is time to separate the
>> althttpd.c code and documentation out into a separate repository
>> (rather than commingling it with the SQLite documentation), get a
>> domain name, and set up a website just for
> Fixed.
Thanks!
> Now with two users, maybe it is time to separate the
> althttpd.c code and documentation out into a separate repository
> (rather than commingling it with the SQLite documentation), get a
> domain name, and set up a website just for althttpd.c :-)
Sounds good to me, though
On 4/26/19, Carl Chave wrote:
> Should "index.cgi" from line number 1923 in subject check in include a
> leading forward slash? My index.cgi scripts aren't being found with
> this version (or any subsequent version) unless I explicitly include
> it as part of the request uri. I added the slash
Hello,
Should "index.cgi" from line number 1923 in subject check in include a
leading forward slash? My index.cgi scripts aren't being found with
this version (or any subsequent version) unless I explicitly include
it as part of the request uri. I added the slash and recompiled and
it started
13 matches
Mail list logo
