• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3271
  • Last Modified:

Your browser sent a request that this server could not understand.

400 bad request
The apache V2.2 httpd.conf have SSL virtual host.
The DocumentRoot directive value is the same as Directory directive (see code snippet).
The URL is http://nohttps.personaDigital.info from FF v3.0.3 and IE v7

<Directory "d:/info.noHTTPS/htdocs">
    Options Indexes FollowSymLinks
    AllowOverride None
    Order allow,deny
    Allow from all
  </Directory>

Open in new window

0
eltonGomez
Asked:
eltonGomez
  • 2
  • 2
1 Solution
 
caterham_wwwCommented:
Can you find something related to the problem in your error.log?
0
 
eltonGomezAuthor Commented:
The error.log: "[Mon Oct 06 04:33:07 2008] [error] [client 190.157.185.1] Invalid URI in request GET / HTTP/1.1"
0
 
caterham_wwwCommented:
Ok, so either r->uri is being unset somewhere or does not start with a lading slash. Since the HTTP_REQUEST header is valid, there must be some internal processing which alters the initial value of r->uri. Since this problem occurs on uri level, your directory container shouldn't be involved.

Are there any directives which are able to modify the uri value of the request? Esp. mod_rewrite or other 3rd-party modules?
0
 
eltonGomezAuthor Commented:
Yes, php module modify the uri value
0

Featured Post

Eye-catchers on the conference table

Challenge: The i-unit group was not satisfied with the audio quality during remote meetings. They were looking for a portable solution with excellent audio quality for use in their conference room but also at their client’s offices.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now