Apache Bad Request Error
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have apache bad request (invalid hostname) Meta Discuss the workings and policies of this site About Us apache bad request 400 Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with apache 400 bad request http https us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only
Org Apache Http Client Httpresponseexception Bad Request
takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Apache2: 400 Bad Request with Rewrite Rules, nothing in error log? up vote 4 down vote favorite 2 This is driving me nuts. Background: I'm using the built-in Apache2 org apache solr common solrexception bad request & PHP that comes with Mac OS X 10.6 I have a vhost setup as follows: NameVirtualHost *:81
Start 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 apache 400 error site About Us Learn more about Stack Overflow the company Business Learn more
Apache 400 Response
about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server
Apache Rlx 400 Review
Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer http://serverfault.com/questions/285964/apache2-400-bad-request-with-rewrite-rules-nothing-in-error-log The best answers are voted up and rise to the top How do I troubleshoot a “Bad Request” in Apache2? up vote 1 down vote favorite I have a PHP application that loads for all URLs except the home page. Visiting "https://my.site.com/" produces a "Bad Request" error message. Any other URL, for example, "https://my.site.com/SomePage/" works just fine. It's only the home page that does not http://serverfault.com/questions/237126/how-do-i-troubleshoot-a-bad-request-in-apache2 work. All pages use mod_rewrite and get routed through a single dispatch script, Director.php. Accessing Director.php directly also produces the "Bad Request" error. BUT- ALL of the other requests go through Director, and they all work just fine, (excluding the home page), so it can't be an issue with the Director.php script? OR can it? I'm not seeing anything in the Apache2 error log, and I'm not seeing any PHP errors in the PHP Error log. I've tried changing the first line of Director.php to read: echo 'test'; exit(); But I still get a "Bad Request". This is the rewrite log for a request to the home page: 123.123.123.123 - - [18/Feb/2011:05:38:49 +0000] [my.site.com/sid#7f273d77cb80][rid#7f273da48b28/initial] (2) init rewrite engine with requested uri / 123.123.123.123 - - [18/Feb/2011:05:38:49 +0000] [my.site.com/sid#7f273d77cb80][rid#7f273da48b28/initial] (3) applying pattern '^/([a-zA-Z0-9\-\_]+)/$' to uri '/' 123.123.123.123 - - [18/Feb/2011:05:38:49 +0000] [my.site.com/sid#7f273d77cb80][rid#7f273da48b28/initial] (3) applying pattern '^/([a-zA-Z0-9\-\_]+)/([a-zA-Z0-9\-\_]+)/$' to uri '/' 123.123.123.123 - - [18/Feb/2011:05:38:49 +0000] [my.site.com/sid#7f273d77cb80][rid#7f273da48b28/initial] (1) pass through / 123.123.123.123 - - [18/Feb/2011:05:38:49 +0000] [my.site.com/sid#7f273d77cb80][rid#7f273da5a298/subreq] (2) init rewrite engine with requested uri /Director.php 123.123.123.123 - - [18/Feb/2011:05:38:49 +0000] [my.site.com/sid#7f273d77cb80][rid#7f273da5a298/subreq] (2) rewrite '/Director.php' -> '-[L,NC]' 123.123.123.123 - - [18/Feb/2011:05:38:49 +0000] [my.site.com/sid#7f273d77cb80][rid#7f273da5a298/subreq] (3) applying pattern '^/([a-zA-Z0-9\-\_]+
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 Business Learn more about hiring developers http://stackoverflow.com/questions/19843588/apache-http-server-post-400 or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Apache Http Server POST 400 up vote 1 down vote favorite 1 that's my first question here. After long research, I decided to ask for help... So first I'll explain my scenario. I have bad request some SOAP web services here. They're consumed by an .Net website. The .Net framework used is in version 4.0. So my web services are configured to accept HTTP/1.0 protocol, due to .Net limitations. In spite of that, everything works fine if I access the service directly to Jboss AS(4.2.2 GA). But, I have to make it work with Apache web server as the receptor of the request. Apache do a inverse proxy redirection to my service, so the site send apache bad request requests to port 8080 (that Apache is listening) and send it to jboss that is expecting the request at port 18080. In many tests, I confirmed that almost every service worked almost fine, sometimes they have the same failure. But one in particular don't work anyway, the request stopped at Apache with status 400 and empty value (the - after the 400) like that: POST /xxxx/xxxx/xxxxx/MyService HTTP/1.1" 400 - "-" "Mozilla/4.0 (compatible; MSIE 6.0; MS Web Service Client Protocol 4.0.30319.296) The other requests that are processed have this value filled. I guess is the response size. Please consider my regards. thanks web-services apache http share|improve this question edited Nov 7 '13 at 18:28 Anders Lindahl 24.7k55275 asked Nov 7 '13 at 18:16 kyogoiano 2118 HTTP error 400 means "bad request", a formal error . Try to look at the request with a network sniffer (such as Wireshark) and compare it with the request for a working service. –Anders Lindahl Nov 7 '13 at 18:33 May you please add some log or error log genereted by the server? Besides, is the server configured to also accept HTTP 1.0 or to only accept it? If this is the case, the line you presented explicitly state the use of HTTP 1.1. That may be the cause... –Filipe Fedalto Nov 7 '13 at 18:33 Dear Anders, thank you for your help, people from infrastructure used wirshar