4chan API, 403?

Why does the 4chan API return 403 in code but if I hit it directly in my browser it's fine?

Any ideas?

        url = 'http://api.4chan.org/b/1.json'
        userAgent = 'Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0'

        headers = {'User-Agent' : userAgent}#'Accept-encoding':'gzip'}

        request = urllib.request.Request(url, headers = headers)
        response = urllib.request.urlopen(request)
        html = response.read()

        print(html)

url = 'http://api.4chan.org/b/1.json'
/polecat kebabs/

>>2
le /g/ face trying to blend in! (OOPS I FORGOT MY LE STYLIZED EXCLAMATION MARK)

Try using Yumina to figure out what's different.

>>4

Yumina? Tried the Google and I get a bunch of fire emblem results

YOU MENA YUMINA

I figured it out.

Adding "accept" header does the trick.

'Accept' : 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',

>>3
awful!!!

>>5
Yumina the Wireshark

Sorry, my mistake for thinking this board would actually be insightful.

Last time I post here

>>10
Bye-ni.

>>10
Sorry buddy, it appears not many others here are using the 4chan api.

Just took a look at the github doc, seems it only works for the imageboards so there's not much point to it.

4chan api
What, you mean HTTP isn't?

Every goddamn website wants to have its own "app" and "API". Fucking useless "web 2.0" hipster shit.

>>10
Where in the 4chan API does it say that this dump is supposed to honor ACCEPT?  Exactly. Now shut up, know your role, and go scrub another mother fucking toilet.

>>15
Can I scrub your anus instead, Kodak-kun?

>>16
Go away princess. Go far far away.

>>14
Oddly enough, I think "APIs" (which I think are poorly, poorly named in this context) could help the Web 2.bullshite, because at some point these people are going to wake up and realize that they aren't using the web anymore, they're just using TCP/IP over the internet, and most of the time they use port 80. (And there are other overlaps as well, but those may fade overtime.) It's going to suck for the first few years, because instead of `Web X.X' the memes you'll be reading about are shit like `Beyond the web!' and `Overcoming the stateless limitations of WWW' and `Paraweb programming' and `Webless XYZ!'  Of course, you'll still access all this shite from a browser, so browsers will now support `meta-web' paradigms and half-assed standards like approved JSON syntaxes for meta-web blogs, etc. etc.

At that point, however, the web will return to what it used to be, and we won't have to put up with all these framework circlejerks anymore.  It won't be a complete healing, and the web never will be as good as it used to be again.  Like newsgroups, it will survive only as a shell of its former self,but at least it won't be getting changed every week by fuckers who just want their names on the LIST OF INNOVATIVE PEOPLE.

>>17
u mad kodak-kun?

Gopher