[Bug 55942] New: 400 - Bad Request on POST (Windows Server 2012 Hyper-V with SSL)

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=55942

            Bug ID: 55942
           Summary: 400 - Bad Request on POST (Windows Server 2012 Hyper-V
                    with SSL)
           Product: Apache httpd-2
           Version: 2.4.4
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_ssl
          Assignee: bugs@httpd.apache.org
          Reporter: ev5unleash@gmail.com

Hello all,

This is my first ever bug report with you guys so bare with me. To give you a
bit of a background, I am currently hosting an application on a WAMP stack. For
redundancy and portability I chose to move the application onto a Hyper-V
Virtual Machine. I went about my business and installed the WAMP stack and made
my configurations. I was careful to keep every configuration precise so I
didn't cause any anomalies. 

Upon finalizing the move onto the new VM, I decided to try it. The operation of
the Application seemed fine on both the un-secure and secure (SSL) vitrualhost.
The problem however is the Apache webserver responding to SSL POST requests.
The server either responds with 400 - BAD REQUEST or with nothing at all. 

My first steps were to verify my configs. In the end, comparing the
configurations from my old server to this new VM and literally copying the
installation over to the VM yield no improvements. So my next step was to look
through the logs. I threw the server into debug mode and observed the logs.
Something I came across was this weird corruption with the POST request. Almost
90% of all POST requests had this corruption which I'll leave an example of
below:

XXX.XXX.XXX.XXX - - [28/Dec/2013:12:00:58 -0500] "3\xebPOST /client/v1/
HTTP/1.1" 200 12
XXX.XXX.XXX.XXX - - [28/Dec/2013:12:00:58 -0500] "EFPOST /client/v1/ HTTP/1.1"
200 12
XXX.XXX.XXX.XXX - - [28/Dec/2013:12:00:57 -0500] "1\x18POST /client/v1/
HTTP/1.1" 200 12
XXX.XXX.XXX.XXX - - [28/Dec/2013:12:00:53 -0500] "E=POST /client/v1/ HTTP/1.1"
200 12
XXX.XXX.XXX.XXX - - [28/Dec/2013:12:00:52 -0500] "C\x85POST /client/v1/
HTTP/1.1" 200 12

Along with these errors core would push an error like the one below:

[Fri Dec 27 22:18:47.803022 2013] [core:error] [pid 1680:tid 4516] [client
XXX.XXX.XXX.XXX:49948] AH00126: Invalid URI in request t\x0cPOST /client/v1/
HTTP/1.1


Now this only seems to be an issue with POSTs over the SSL-connection. The
POSTs over unsecure connections seems fine however. 

In the end, I've pretty much isolated every variable I could think of. The only
thing I see changing is the difference of running the WAMP stack on a physical
machine as opposed to a Hyper-V Virtual Machine. So after a week of digging
around the interwebs, consulting my more tech-literate friends, and spending
hours troubleshooting, I am at a loss. 

Any help would be much appreciated!





My configurations are below:

Physical Box (that works perfectly)

Intel Core i3-3217U
2x4GB of RAM (8 total)
120GB Muschkin SSD 
Intel Gigabit NIC
Windows 7

Virtualization Machine
Intel Core i5-4430
2x4GB of RAM (8 total)
128 SSD
Inttel Gigabit NIC
Windows Server 2012

Virtualization Box
4 GB RAM
80 GB Disk Space
Microsoft Virtual Switch NIC
Windows 7

[I have tried countless operating systems and other Virtualization boxes. All
which have had the consistent issue]
[Other OSes I have tried for the Virtual Machine]
[Windows 7]
[Windows 8]
[Windows 8.1]
[Windows Server 2008 R2]
[Windows Server 2012]
[Windows Server 2012 R2]

[Other OSes I have tried with HyperV host]
[Windows Server 2012]
[Windows Server 2012 R2]

[Again I have tried a totally different box for hosting these VMs as well]

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org