As mentioned in other answers, InvalidBadResponse is due to Javascript failure.
Problem:
The reason it was unsuccessful for me was because the ajax libraries for ASP.NET needed to run did not load; take a look at your javascript debugger browser; this is what mine (in Chrome) looked like

As you can see, the .axd files .axd not serviced, and the ASP.NET Ajax client-side framework failed to load error was quite complicated.
Reason: (in my case)
I had a url rewrite rule that accidentally changed the .axd , which caused them to not be served.
I would recommend checking your web.config , add a line if necessary
<add input="{URL}" pattern="\.axd$" negate="true"/>
to your rules and this
routes.Ignore("{resource}.axd/{*pathInfo}");
in your Global.asax (if you have one), where (and if) you are registering routes.
Check this SO answer: On the Ajax client side, Asp.Net 4.0 failed to load
James
source share