request_streams needs to send a User-Agent header

Laith- / lightopenid

Automatically exported from code.google.com/p/lightopenid

0 stars 0 forks source link

request_streams needs to send a User-Agent header #55

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

Any HTTP request sent to LiveJournal without a User-Agent header will fail, so 
LightOpenID needs to add one for maximum compatibility. As I understand it, 
LiveJournal added this check to help fend off DDoS attacks they've been getting.

Original issue reported on code.google.com by pikadude...@gmail.com on 16 Jan 2012 at 9:40

GoogleCodeExporter commented 9 years ago

And what user agent would that be?
Lying that one is, for example, firefox isn't a good idea (because it skews 
statistics if they make them), and unknown user-agents might be blocked as well.

Original comment by mewp...@gmail.com on 16 Jan 2012 at 10:00

GoogleCodeExporter commented 9 years ago

I've only tried "PHP" in my tests; LiveJournal is OK with that.

Original comment by pikadude...@gmail.com on 16 Jan 2012 at 10:10

GoogleCodeExporter commented 9 years ago

Issue 57 has been merged into this issue.

Original comment by mewp...@gmail.com on 10 Feb 2012 at 3:47

GoogleCodeExporter commented 9 years ago

I wonder if that might be related to issue 46. Sourceforge is known to prevent 
access to normal webpages if the User-Agent is either blank or in a black list. 
So if you want to download Sourceforge Webpages, you have to set the user agent 
header to something (preferable something unique). I don't know if that is 
related to openid at all.

Original comment by HendrikU...@nexgo.de on 20 Feb 2012 at 1:50