php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #57302 Dump of full Http Message of current request
Submitted: 2006-10-17 17:56 UTC Modified: 2007-02-15 09:38 UTC
From: clay at killersoft dot com Assigned: mike (profile)
Status: No Feedback Package: pecl_http (PECL)
PHP Version: 5.2.0 RC4 OS: Any
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: clay at killersoft dot com
New email:
PHP Version: OS:

 

 [2006-10-17 17:56 UTC] clay at killersoft dot com
Description:
------------
I'd like to be able to easily access the entire HttpMessage of 
the request that brought the user to the current script.

Presently, it seems like the only way to get at that data 
using this extension is with http_get_request_headers() and 
http_get_request_body(). 

To re-create the raw HttpMessage, that puts me in the position 
of having to loop through the array that 
http_get_request_headers() returns.


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2006-10-18 03:12 UTC] mike@php.net
This would require a huge amount of SAPI related code and create build deps on the used SAPI.  I also think it would be just as much guessing like it is currently.

What pecl/http does ATM is, that it grabs all HTTP_* env vars to build the request headers.  For the request body, it checks whether PHP has already read in the "raw post data" and if not, eg. because PHP dind't like the request method, we catch that up.

That said, only the webserver software knows the real raw request message and AFAICS we can't really do better than now.
 [2006-10-20 06:58 UTC] mike@php.net
Anything to add here?
 [2007-01-12 10:47 UTC] mike@php.net
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.


 
PHP Copyright © 2001-2019 The PHP Group
All rights reserved.
Last updated: Sun Aug 25 18:01:28 2019 UTC