durusmail: quixote-users: Inconsistency between mod_scgi behavior and published scgi protocol?
Inconsistency between mod_scgi behavior and published scgi protocol?
2008-06-23
Inconsistency between mod_scgi behavior and published scgi protocol?
Inconsistency between mod_scgi behavior and published scgi protocol?
2008-06-23
2008-06-24
Inconsistency between mod_scgi behavior and published scgi protocol?
Neil Schemenauer
2008-06-23
Al Pacifico  wrote:
> I've been writing a SCGI server program in C (for use as a web service) and
> while testing, I came across the following when fetching the URL '
> http://localhost/dynamic': mod_scgi passes a SCGI header with name
> QUERY_STRING and an empty value (i.e. name NUL  NUL).

I'm not sure what is specified by the HTTP RFC but the vast majority
of web sites, AFAIK, treat an emtpy query string the same as no
query string.  The behavior of mod_scgi is the same as mod_cgi in
regards to QUERY_STRING.  If you really want to distinguish between
no query string and an empty query string, I guess you could look
for a '?' character in REQUEST_URI.

> I wonder if mod_scgi should be modified. I think mod_scgi should
> omit the query string header if there is no query string.

I don't think so.  That behavior would be surprising to people
coming from other systems.  Is there some use case you foresee?

Regards,

  Neil

reply