Re: ssl problems, posted by Olaf Kasten on Mon Feb 13 21:44:05 2012
|
> > well it's not a server but my laptop, but yeah, the elog server and the browser ran on the same machine, no iptables.
>
> Strange: I thought I was able to reproduce your problem, but no: whatever browser I try I can access ELOG with SSL if
|
|
Re: ssl problems, posted by John Doroshenko on Tue Feb 14 00:55:58 2012
|
Andreas Luedeke wrote:
|
|
Re: ssl problems, posted by Andreas Luedeke on Tue Feb 14 14:54:06 2012
|
John Doroshenko wrote:
|
|
Re: ssl problems, posted by Diego on Tue Feb 14 17:17:44 2012
|
Andreas Luedeke wrote:
|
Re: ssl problems, posted by John Doroshenko on Tue Feb 14 20:41:08 2012 
|
John Doroshenko wrote:
|
|
Re: ssl problems, posted by Stefan Ritt on Thu Feb 16 18:10:33 2012
|
Yes, there is a new feature called record splitting which causes the browser to send the "G" of the "GET ..." in a dedicated TCP
package. This started in FF10, Chrome 17, and it will come in others as well. It only affects direct SSL connections (SSL=1). I fixed the bug in SVN revision
#2435. Please update also MXML to revision #73. Let's hope that surprises like that will not happen too often. |
|
Re: ssl problems, posted by John Doroshenko on Thu Feb 16 23:56:35 2012
|
Stefan Ritt wrote:
Yes, there is a new feature called record splitting which causes the browser to send the "G" |
|
Re: ssl problems, posted by Stefan Ritt on Mon Feb 20 14:53:04 2012
|
Stefan Ritt wrote:
Yes, there is a new feature called record splitting which causes the browser to send the "G" |