Commits
- Commit:
a1e159c917d4cc0bf27e3faedf69e8d720162936
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix PATH_INFO / SCRIPT_NAME splitting
- Commit:
03d671e2aa44271e6feb5dc6b1f20f833735d917
- From:
- Omar Polo <op@omarpolo.com>
- Date:
implement fastcgi strip number
- Commit:
4f7492c36e5ae600b0e0ad2b2d271712d55e34b9
- From:
- Omar Polo <op@omarpolo.com>
- Date:
lower debug log priority
- Commit:
b27dc2b0a33b5087f2c505b82dcf2cc73208dcaa
- From:
- Omar Polo <op@omarpolo.com>
- Date:
draft the PATH_INFO and SCRIPT_NAME handling
The idea is to require SCRIPT_NAME to be defined and strip it from
the beginning of the path to get PATH_INFO. Soon(tm) a `fastcgi
request strip' option will be added too. Maybe even `fastcgi script
name "path"` that sets SCRIPT_NAME automatically.
- Commit:
a1ba9650a9f0cc0d9e70800d71769d32f927b939
- From:
- Omar Polo <op@omarpolo.com>
- Date:
revamp fastcgi configuration: make it per-location
this revamps the syntax in the configuration to better match httpd(8)
(and in general be less weird) and to allow per-location fastcgi
configurations.
the bare `param' is now deprecated, but for compatibility it acts
like `fastcgi param' would do now. Same story for `fastcgi <pathÂ>'.
- Commit:
0f7fdd21050e3795db896b99e542523c84e075d7
- From:
- Omar Polo <op@omarpolo.com>
- Date:
parse (and log) the header from fastcgi
- Commit:
fef06f06ac4779731bb8e293248eae1883a7ed1b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
remove the fcgi debug code
- Commit:
ed164e7221f75d3d7f48351e9427f2ce53ab284a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
call getnameinfo() only once per request
- Commit:
eac9287d295719131cbc346503dd2a0612e54b4b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
copyright years++
- Commit:
509d0509a50883a6f8407b63774f40dd1e41dadf
- From:
- Omar Polo <op@omarpolo.com>
- Date:
implement `listen on'
Listening by default on all the addresses is so bad I don't know
why I haven't changed this before. Anyway.
Add a `listen on $hostname port $port' syntax to the config file
and deprecate the old "port" and "ipv6" global setting. Still try
to honour them when no "listen on" directive is used for backward
compatibily, but this will go away in the next next version hopefully.
At the moment the `listen on' in server context don't filter the
host, i.e. one can still reach a host from a address not specified
in the corresponding `liste on', this will be added later.
- Commit:
2dd5994ae172ed8162aff397b907e4fc476fbaae
- From:
- Omar Polo <op@omarpolo.com>
- Date:
use fatal() in code used in the daemon
- Commit:
eae52ad493f582222b4f2b748c0043c42bb851cb
- From:
- Omar Polo <op@omarpolo.com>
- Date:
switch to the more usual log.c
- Commit:
281a8852b3a2d76c10d2fb6476a706746d05509b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
rename log.[ch] to logger.[ch]
- Commit:
df5058c919cbd1538d0a04cb2a4c179c0291566f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
provide a more usual fatal
fatal usually appends the error string. Add 'fatalx' that doesn't.
Fix callers and move the prototypes to log.h
- Commit:
97b306cbee6d105885a761e04274f661a0ec3757
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add an implicit fastcgi parameter: GEMINI_SEARCH_STRING
it’s the QUERY_STRING decoded if it’s a search-string (i.e. not a
key-value pair.) It’s useful for scripts to avoid percent-decoding
the querystring in the most common case of a query, because in Gemini
querystrings key-value paired are not common.
Idea from a discussion with Allen Sobot.