Re: SSL & POCO::CLIENT::HTTP

Works fine here. Are you using POE::Component::Client::HTTP 0.84?

HTTP/1.1 200 OK
Cache-Control: private
Date: Sun, 08 Jun 2008 00:16:07 GMT
Server: Microsoft-IIS/6.0
Content-Length: 498
Content-Type: text/html; charset=utf-8
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Redirect to news site</TITLE>
<link href="StyleSheets.css" rel="stylesheet" type="text/css" />
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=Windows-1252">
</HEAD>
<BODY>



 Loading . . . 

<Script Language="JavaScript">
top.location="http://news.tabonline.co.za/"
</script>

</BODY>
</HTML>

-- Rocco Caputo - http://poe.perl.org/

Comment on Re: SSL & POCO::CLIENT::HTTP

Replies are listed 'Best First'.
Re^2: SSL & POCO::CLIENT::HTTP by avo (Pilgrim) on Jun 09, 2008 at 08:32 UTC
I wasn't using 0.84 which has solved the issue on linux. But on Windows (Using ActiveState Perl 5.10) I have now a bigger issue. The SSLify module can not set the socket to be blocking using the IO::Handle's blocking(1) method (&Set_Blocking). I see that there is a work around on internet of dealing with blocking sockets and win 32 which is working somehow on ActiveState Perl 5.10 (here). But I am not sure how to apply this patch... Can you help me please. Please try using https://www.tabonline.co.za/ in the test. I gave it a shot but after overriding the socket blocking mode like that I am now getting Bad Request "incomplete response" ... Looks like HTTP.pm doesn't read anything from this socket. Funny enough looks like from time to time it does. Very strange. Please help! UPDATE: Herewith a hint on the problem... experienced in a different environment - same issue...	[reply]
Re^3: SSL & POCO::CLIENT::HTTP by rcaputo (Chaplain) on Jul 28, 2008 at 19:13 UTC
Please submit your information to POE::Component::Client::HTTP's request tracker at rt.cpan.org. There are a few benefits (and few, if any drawbacks) from using the official but tracker: (a) Requests stay organized and in a place I'm sure to find them later. (b) Your request isn't lost in a sea of web pages. (c) You will be notified by e-mail when the status of your request changes. (d) Possibly some other stuff, but it's all good. The Perl community offers rt.cpan.org as a resource for CPAN authors, and the users who love (and, to be honest, hate) their modules. Thanks for working with us to make Perl and CPAN a better place for tomorrow. `-- Rocco Caputo - http://poe.perl.org/`	[reply]


The stupid question is the question not asked
	PerlMonks