Bug 48354 - void ap_custom_response is not supporting the binary data
Summary: void ap_custom_response is not supporting the binary data
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.2.14
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2009-12-08 15:31 UTC by amar.sharma
Modified: 2018-11-07 21:09 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description amar.sharma 2009-12-08 15:31:42 UTC
void ap_custom_response (request_rec *r, int status, char *string);

If we need to creat a custome respons with some binary data (for example gif file) then in that case the third arguement should take the binary stream. But this is not taking the binary data as third arguement and hence end web client (browser) is not showing the binary data.

Moreover, content type is always Text/html and content length is seeting wiht incorrect value
Comment 1 Jeff Trawick 2009-12-08 16:28:48 UTC
You want a new API in some future httpd release that provides more extensive capabilities than ap_custom_response().  I suggest discussing this on the dev mailing list (http://httpd.apache.org/lists.html#http-dev).
Comment 2 William A. Rowe Jr. 2018-11-07 21:09:50 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.