Are you running multiple virtual host? I'm not sure if this has anything to
do with the bug but I've temporarily disabled all virtual host so that I'm
only using a single virtual host and have yet been able to replicate the
bug. Then again, this bug only seems to present itself once apache has b
I have done some research on this subject and found the following. The error
only occurs for me when making HTTPS request. If I make an HTTP request I
never experience this issue. Additionally I've found that setting a
content-type header alleviates the problem. Specifically setting the
charse
