Re^2: 500 EOF when chunk header expected

same results with timeout commented. this is a spammer drop page, and i operate http://www.uribl.com, which trie to identify spammer uri's by doing heuristics on their landing pages.... however, i have recently seen an increase in the 500 EOF's, which appears to me like the spammers are doing something sneaky to try to avoid automated detection. i may give WWW::Mechanize a go, and if I have to, revert out to a syscall for wget, but this almost has to be something wrong with LWP dont you think? thanks! d

Comment on Re^2: 500 EOF when chunk header expected

Replies are listed 'Best First'.
Re^3: 500 EOF when chunk header expected by marto (Cardinal) on Oct 25, 2005 at 17:46 UTC
The URL you have given is http://avantgardeconcierge.com which as I said has a frame which opens http://www.golbit.com. The next point in this trail seems to be http://www.tenderise.net seems to do a few things (http://www.tenderise.net/ms/?bb for example, I assme this does some sort of reirect) then fails. Im not sure exactly what your trying to achieve, but this does not work from lynx (on my remote netbsb box) or firefox (local), so I wouldnt expect LWP to be any different. If these are your domains why not check the log files to get a better idea of what is going on? Hope this helps Martin	[reply]
Re^4: 500 EOF when chunk header expected by dallase (Initiate) on Oct 25, 2005 at 18:04 UTC
hi martin.. if you read my message that you replied to, i state my purpose there. thanks!	[reply]
Re^5: 500 EOF when chunk header expected by marto (Cardinal) on Oct 25, 2005 at 18:54 UTC
dallase, I did read your message, hence my reply. I am not familiar with the term 'spammer drop page' or 'landing pages', which you do not go on to explain. I google'd these terms and didnt find anything that seemed to relate to the subjet in hand. Perhaps its just me, or perhaps you could have provided a more detailed explanation of what was going on. Regardless, whatever these 'spammer drop page' or 'landing pages' are, this is not immediately related to the problem you had reported. In your original post mentions that you can see the url properly in a web browser and by using wget. This is contrary to my findings. I notice you are new here, welcome. Have you read How (Not) To Ask A Question or the PerlMonks FAQ? If not they are worth a read Cheers, Martin	[reply]