fb iframe application: 405 error

Question

my application works fine without iframe, returns 405 error at facebook! why is it so?

score 16 · Answer 1 · answered Mar 14 '11 at 13:27

16

For reference I had this same 405 error. This was because my Facebook app was pointing to a .html file for testing.

I renamed to .aspx and my server stopped sending that error back to Facebook

answered Mar 14 '11 at 13:27

Vaynag

Thank you, this was my issue just now. – Jonathan May 12 '11 at 06:39
1

Very good answer, to use an extension that's POSTable to by the web server. I'm unable to configure my host's web server so this answer works best for me: to change the page extension over which I do have control. Thanks. My guess is that .PHP and other dynamic page extensions would work too. – John K Feb 29 '12 at 02:10
if it still does not work for you, check the default file for aspx pages. in my case it was default.aspx, so simply renaming my index.html to index.aspx did not work. once I added index.aspx as a default, it started working. – lasaro Aug 13 '12 at 17:24
This worked for me. Somewhat annoying that this is required though - not sure why Facebook won't accept an index file with a .html extension. Not all Facebook apps require complex server side code – Craig Myles Feb 11 '13 at 07:12

score 1 · Accepted Answer · answered Jan 24 '11 at 18:03

1

Disable POST for Canvas on the application settings, under the "advanced" tab.

answered Jan 24 '11 at 18:03

Julio Santos

1

Ideally, you should prepare for it. Check out FB's dev blog and the roadmap. – Julio Santos Jan 24 '11 at 23:27
is this still possible? i don't see that setting in the application settings. – split19 Nov 15 '12 at 17:33
@split19 POST for canvas is now default for all apps. This referred to a temporary reversal available at the time. – Julio Santos Nov 19 '12 at 08:48

score 0 · Answer 3 · answered Jul 11 '16 at 11:34

0

When using nginx server, this can be caused by pointing root of the web to .html file... Change it e.g to .php and it will work.

This is probabl because nginx does not allow POST method on static websites.

answered Jul 11 '16 at 11:34

Zdenek Hatak

3 Answers3