Using fsockopen instead of PEAR's HTTP_Request class
Posted: Fri Jan 13, 2006 1:33 pm
Hi there,
Garvin recently threw together a new event ( backend_http_request ), when coupled with his serendipity_event_proxy_request plugin, it allows the user to specify whatever HTTP proxy settings they require for making outbound HTTP requests. This is great (Thanks Garvin!)!
But there is one small problem - serendipity_reference_autodiscover and _serendipity_send don't use the PEAR HTTP_Request class and instead do some hand-crafted HTTP requests. Is there a compelling reason for this, or can they be changed to also use HTTP_Request method?
I'm going to have a little poke around and see what happens when I make this change (or indeed, if this change is possible).
Feedback gratefully received!
Martin
Garvin recently threw together a new event ( backend_http_request ), when coupled with his serendipity_event_proxy_request plugin, it allows the user to specify whatever HTTP proxy settings they require for making outbound HTTP requests. This is great (Thanks Garvin!)!
But there is one small problem - serendipity_reference_autodiscover and _serendipity_send don't use the PEAR HTTP_Request class and instead do some hand-crafted HTTP requests. Is there a compelling reason for this, or can they be changed to also use HTTP_Request method?
I'm going to have a little poke around and see what happens when I make this change (or indeed, if this change is possible).
Feedback gratefully received!
Martin