On 10/21/2015 09:54 AM, Andy Wang wrote:
On 10/21/2015 09:31 AM, Yann Ylavic wrote:
OK, thanks :)
Andy, can you give the proposed patch a try?
I will do that today.
And thank you to Rudiger and yourself, and everyone else on the thread
for all the help.
I missed the trailing 0x0a in the different wireshark captures. I was
trusting wireshark's http dissection rather than looking at the raw hex
data and it didn't show the trailing \n.
I gotta go back to the basics and lean less on wireshark's
"intelligence" :)
Oh, and the plugin developer actually identified where the \n was coming
from and has resolved it on the client end.
I do have one question. Any idea why this only occurs on Windows servers?
Andy
