Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP Error 403: Forbidden #1

Open
twigbranch opened this issue Dec 21, 2012 · 4 comments
Open

HTTP Error 403: Forbidden #1

twigbranch opened this issue Dec 21, 2012 · 4 comments
Assignees

Comments

@twigbranch
Copy link

Getting repeated "HTTP Error 403: Forbidden" and no ranking results. Any idea why?

@jparise
Copy link
Owner

jparise commented Dec 21, 2012

Everything appears to be working for me. Are you perhaps outside of the United States in a country without an official App Store presence?

@ghost ghost assigned jparise Dec 21, 2012
@twigbranch
Copy link
Author

In the US. But looks like they banned my IP- not sure why, is running this 2-4 times / day excessive?

Monkey patching with this code allows you to choose a different source IP if available:
http://stackoverflow.com/questions/1150332/source-interface-with-python-and-urllib2

Beyond this- I'm noticing a number of 301 redirect using the itunes.apple.com url as-is.

@twigbranch
Copy link
Author

It appears that after numerous requests with the various genre and store IDs which are met with 301 redirects, the IP becomes banned, and instead receives 403 forbidden. I'm wondering if the requests are coming in too quickly so it exceeds some threshold they set.

jparise added a commit that referenced this issue Feb 3, 2013
This is controlled via a new `--source` command line argument.  This
feature is only available for Python 2.7 and later.

See #1
@jparise
Copy link
Owner

jparise commented Feb 3, 2013

I just pushed a change that allows the HTTP connection's source address to be set using a new command line argument: --source. Hopefully that will make it easier for you to work around the problems that you're seeing.

I don't have any new information to share about the larger problem, however. I'm definitely open to suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants