DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8587>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8587
Porting Apache Modules from Apache v1.3 to 2.0 (HTTP Headers)
Summary: Porting Apache Modules from Apache v1.3 to 2.0 (HTTP
Headers)
Product: Apache httpd-2.0
Version: 2.0.35
Platform: Other
OS/Version: Solaris
Status: NEW
Severity: Normal
Priority: Other
Component: Other Modules
AssignedTo: bugs@httpd.apache.org
ReportedBy: cm@cmunt.demon.co.uk
This issue concerns the porting of Apache modules from Apache 1.3 to 2.0.
I have a module in which the content handler sends the HTTP request information
to an Application Server and returns the subsequent response from the
Application Server to the client.
The Application Server is responsible for constructing the complete HTTP
response, including the HTTP headers. The module simply relays the response to
the client using the ap_rputs() function.
The problem with Apache v2.0 is that it always assumes responsibility for
constructing and dispatching an HTTP header. For our module, the consequence of
this behavious is that the client receives two blocks of HTTP headers - those
generated by Apache and those generated by the Application Server. Earlier
versions of Apache would not automatically return HTTP headers to the
client unless you explicitly told it to (via the ap_send_http_header()
function).
The question is, is there any way of suppressing the headers delivered by Apache
v2.0 for a content handler ? What's needed is (sort of) the equivalent of the
CGI 'nph-' directive. It would be nice to not have to strip out the HTTP
headers returned by the Application Server, just for the purpose of setting them
individually through the various Apache 'set HTTP header' functions.
BTW, on a separate but not totally unrelated note: some proper documentation for
the Apache v2.0 API would be welcome !
Thank you in advance.
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8587>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8587
Porting Apache Modules from Apache v1.3 to 2.0 (HTTP Headers)
Summary: Porting Apache Modules from Apache v1.3 to 2.0 (HTTP
Headers)
Product: Apache httpd-2.0
Version: 2.0.35
Platform: Other
OS/Version: Solaris
Status: NEW
Severity: Normal
Priority: Other
Component: Other Modules
AssignedTo: bugs@httpd.apache.org
ReportedBy: cm@cmunt.demon.co.uk
This issue concerns the porting of Apache modules from Apache 1.3 to 2.0.
I have a module in which the content handler sends the HTTP request information
to an Application Server and returns the subsequent response from the
Application Server to the client.
The Application Server is responsible for constructing the complete HTTP
response, including the HTTP headers. The module simply relays the response to
the client using the ap_rputs() function.
The problem with Apache v2.0 is that it always assumes responsibility for
constructing and dispatching an HTTP header. For our module, the consequence of
this behavious is that the client receives two blocks of HTTP headers - those
generated by Apache and those generated by the Application Server. Earlier
versions of Apache would not automatically return HTTP headers to the
client unless you explicitly told it to (via the ap_send_http_header()
function).
The question is, is there any way of suppressing the headers delivered by Apache
v2.0 for a content handler ? What's needed is (sort of) the equivalent of the
CGI 'nph-' directive. It would be nice to not have to strip out the HTTP
headers returned by the Application Server, just for the purpose of setting them
individually through the various Apache 'set HTTP header' functions.
BTW, on a separate but not totally unrelated note: some proper documentation for
the Apache v2.0 API would be welcome !
Thank you in advance.