Bad Request Invalid Header Name Error
Contents |
the stand-alone Adblock Plus app on Android Post a reply 7 posts • Page 1 of 1 Bad Request - Invalid Header (Android) by vdn20 » Wed Dec 04, 2013 9:07 pm I'm having a problem accessing the newegg.com when Adblock Plus is bad request invalid header android on my tablet. When it is off, it works fine though. My device is the HP
Bad Request - Invalid Header Fiddler
Touchpad running CM10, Android version 4.1.2, it is rooted, ABP version 1.2.0.309 build #309, and filter EasyList. Is anyone else having this problem? bad request - invalid verb http error 400. the request verb is invalid Thanks vdn20 Posts: 3Joined: Wed Dec 04, 2013 8:56 pm Top Re: Bad Request - Invalid Header (Android) by abakus » Fri Dec 06, 2013 12:12 pm Hey,can not reproduce your problem, everything works fine here. Do you bad request invalid host name have maybe some other information that can help to find the problem?greetz,abakus abakus Posts: 192Joined: Wed May 08, 2013 1:34 pm Top Re: Bad Request - Invalid Header (Android) by vdn20 » Sat Dec 07, 2013 3:21 am I'm not sure what other kind of information I should provide, or where to look for that matter. I just know that when ABP is active, I can't access newegg.com, but oddly enough, I just tried newegg.ca and it
Bad Request Invalid Verb Sharepoint
worked, and not newegg.com seems to work, not sure what happened though. I thought that ABP may have stopped working, which I have seen happen before in the past where ads that were usually blocked showed up, which I end up fixing by turning off and on ABP, but that doesn't seem to be the case, it still worked. I'm not sure if this is relevant or not, but when I click on links from a newegg e-mail, it was the same, but it seems to be working now for some reason right now.Just tried it again, and it's not working again. Tried newegg.ca just for fun, which worked, and then tried newegg.com, which didn't work. Same thing for the newegg links from an e-mail. I just get the same error I've always been getting.Bad Request - Invalid HeaderHTTP Error 400. The request has an invalid header name.If there is some other kind of information you would like me to provide, let me know, otherwise I'm not sure what to provide.Thanks vdn20 Posts: 3Joined: Wed Dec 04, 2013 8:56 pm Top Re: Bad Request - Invalid Header (Android) by Bobo2 » Fri Dec 20, 2013 2:54 pm I've had the same problem on 2 devices for several weeks and have just solved it by clearing the Adblock local data in Android app manager then clearing Chrome private data in the browser. I
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company bad request invalid verb chrome Business Learn more about hiring developers or posting ads with us Stack Overflow Questions http error 400. the request has an invalid header name fiddler Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million
Http Error 400. The Request Has An Invalid Header Name Android
programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Fiddler POST Invalid Header Name up vote 0 down vote favorite I am sending a POST request to a WCF Web https://adblockplus.org/forum/viewtopic.php?t=19733 service using fiddler, and the service responds with HTTP 400: The request has an invalid header name. The post request looks like this: User-Agent: Fiddler Host: localhost:49392 Content-Type: application/json Content-Length: 0 { "clientFirstName" : "John"} My endpoint is defined as follows: [OperationContract] [System.ServiceModel.Web.WebInvoke (Method = "POST", RequestFormat = WebMessageFormat.Json, ResponseFormat = System.ServiceModel.Web.WebMessageFormat.Json, BodyStyle = System.ServiceModel.Web.WebMessageBodyStyle.Wrapped, UriTemplate = "MakeReservation")] String MakeReservation(Stream reservationStream); MORE First of all, the JSON was in the wrong pane. I moved http://stackoverflow.com/questions/25862178/fiddler-post-invalid-header-name it to the Request Body pane. I changed the prototype of the function to take a String instead of Stream as the input parameter. The service now accepts my call and returns 200, but in the debugger I see that the input parameter String is null. When I change it back to Stream, I get 400 again. YET MORE Enable tracing gives me at trace file with the following message: Incoming message for operation 'MakeReservation' (contract 'ITalLimoService' with namespace 'http://tempuri.org/') contains an unrecognized http body format value 'Json'. The expected body format value is 'Raw'. This can be because a WebContentTypeMapper has not been configured on the binding. See the documentation of WebContentTypeMapper for more details. As noted int the WebInvoke definitiuon, both the RequestFormat and ResponseFormat are set to WebMessageFormate.Json. Why is IIS complaining about this? wcf rest fiddler share|improve this question edited Sep 17 '14 at 6:47 asked Sep 16 '14 at 6:42 Aharon Manne 403819 The data in your first block is malformed; you are showing JSON text in the headers, and you have a Content-Length: 0 when you are clearly sending content. Please update your question so we can see exactly what you're doing. –EricLaw Sep 20 '14 at 12:02 add a comment| 2 Answers 2 active oldest votes up vote 1
Web Platform Installer Get Help: Ask a Question in our Forums More Help Resources Blogs http://forums.iis.net/t/1092969.aspx?Bad+Request+Invalid+Header+Name+problem+using+IIS+6+0 Forums Home IIS.NET Forums IIS 5 & IIS 6 Extensibility Bad Request (Invalid Header Name) problem using IIS 6.0 Bad Request (Invalid Header Name) https://bugzilla.mozilla.org/show_bug.cgi?id=1144221 problem using IIS 6.0 RSS 1 reply Last post Mar 29, 2007 03:47 PM by ApurvaJoshi ‹ Previous Thread|Next Thread › Print Share Twitter bad request Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Advanced Search Reply wanderlusted 1 Post Bad Request (Invalid Header Name) problem using IIS 6.0 Mar 29, 2007 10:53 AM|wanderlusted|LINK Hi, I'm trying to call a webservice from amoble phone using java ME. I have exactly the same webservice bad request invalid running on Win XP PRO (IIS5) and Win Server 2003 (IIS 6).With the first one everything is fine, but on IIS6, I got the following error:
Bad Request (Invalid Header Name)
According to Microsoft: ( http://support.microsoft.com/kb/828726) In Microsoft Internet Information Services (IIS) 6.0, when a request contains a header name that includes a question mark (?) character or another separator character, Http.sys rejects the request and sends the following error message to the requestor: Bad Request (Invalid Header Name). Here is my request:newegg.com returns HTTP Error 400 Invalid Header Status: NEW Whiteboard: Keywords: Product: Firefox for Android Classification: Client Software Component: General (show other bugs) Version: unspecified Platform: x86_64 Linux Importance: -- normal (vote) TargetMilestone: --- Assigned To: Nobody; OK to take it and work on it QA Contact: TriageOwner: Mentors: URL: Depends on: Blocks: Show dependency tree /graph Reported: 2015-03-17 10:23 PDT by Gene Wood [:gene] Modified: 2015-06-04 12:51 PDT (History) CC List: 2 users (show) gene kdubost See Also: 980564 Crash Signature: (edit) QA Whiteboard: Iteration: --- Points: --- Has Regression Range: --- Has STR: --- Tracking Flags: Attachments Add an attachment (proposed patch, testcase, etc.) Description Gene Wood [:gene] 2015-03-17 10:23:33 PDT Firefox for Android 36.0.2 Steps to reproduce : Browse to http://www.newegg.com/ Click the "Computer Hardware" menu item on the left (or any menu item) Expected results : Be taken to the Computer Hardware page Actual results : HTTP Error 400 Bad Request - Invalid Header The request has an invalid header name This happens for any link clicked Once this occurs, even browsing to http://www.newegg.com/ results in the same HTTP 400 error I've observed this for as long as I can remember but only gotten to reporting it here now. Comment 1 Gene Wood [:gene] 2015-05-20 10:21:01 PDT I've reported this on webcompat as well now : https://webcompat.com/issues/1123 Comment 2 Karl Dubost :karlcow 2015-05-25 01:56:22 PDT This bug is not clear if the user receives the Desktop or the mobile site. See Bug #980564 I can't reproduce the current bug for now. Comment 3 Gene Wood [:gene] 2015-05-26 09:30:42 PDT When browsing with Firefox on Android 38.0.1 I get the Desktop site and this error occurs. Comment 4