I saw on on the bug report for this that someone said they started using polarssl instead of openssl and that solved it. Can anyone confirm that? Did that take care of it?
Tony Z On Thu, Mar 31, 2011 at 7:31 PM, Tony Zakula <[email protected]> wrote: > Well on ecommerce sites, https is a must for transactions, and when clients > are getting garbage when trying to complete their order, it is unacceptable. > I love using Cherokee, but have been unable to use it because of this. > > > On Thu, Mar 31, 2011 at 7:07 PM, Keith <[email protected]> wrote: > >> I wouldn't worry about using it for production. I'm running several >> massive sites with it, with very few hiccups, for over a year now. >> >> Turning off chunked encoding definitely solved the issue; which hadn't >> even been an issue until last week. It would be nice to turn it off per >> vhost, or even from a rule; rather than across the whole server. But >> whatever. At least everything back to running. >> >> ------------------------------ >> >> Tony Zakula <[email protected]> >> March 31, 2011 6:51 PM >> >> Well that is good news. So turning off chunked encoding fixed it? I have >> been waiting to use Cherokee in production because of that https issue. It >> is the only bug holding me back. At least there is a way to work around it >> possibly. >> >> On Thu, Mar 31, 2011 at 6:43 PM, Keith <[email protected]>wrote: >> >>> It was only happening under HTTPS. But that script only runs in the >>> admin, which I am serving via HTTPS. So... >>> >>> ------------------------------ >>> >>> Tony Zakula <[email protected]> >>> March 31, 2011 6:40 PM >>> >>> >>> I've been running a Cherokee server on Ubuntu 10.10, with PHP 53 >>>> serving Wordpress for the last 6 months or so. I've been keeping Cherokee >>>> up >>>> to date pretty much since v0.9. >>>> >>>> But with 1.2.2, I'm having the Wordpress admin panel throwing errors >>>> with 'load-scripts.php' and 'load-styles.php'. Those scripts basically >>>> combine js and css files into single large requests. I was seeing those >>>> files suddenly coming through cut off, or having garbage characters thrown >>>> on the end (that might have been from the browsers choking on them). >>>> Firefox >>>> and Safari were being affected, Chrome wasn't having the issue. At first, I >>>> though it was a gzip issue. But turning it off wasn't fully resolving the >>>> issue. What stopped it was turning off 'Chunked Encoding' on the server >>>> connections. Haven't seen the issue again after that. >>>> >>>> So is 'Chunked Encoding' know to be broken on 1.2.2, or could it be >>>> causing issues in combination with some other problem I might have? >>>> >>>> Thanks >>>> >>> >>> Wow! Interesting. Were you by chance seeing these errors under https >>> or http? >>> >>> Thanks! >>> >>> Tony Z >>> _______________________________________________ >>> Cherokee mailing list >>> [email protected] >>> http://lists.octality.com/listinfo/cherokee >>> ------------------------------ >>> >>> Keith <[email protected]> >>> March 31, 2011 3:01 PM >>> >>> I've been running a Cherokee server on Ubuntu 10.10, with PHP 53 serving >>> Wordpress for the last 6 months or so. I've been keeping Cherokee up to date >>> pretty much since v0.9. >>> >>> But with 1.2.2, I'm having the Wordpress admin panel throwing errors with >>> 'load-scripts.php' and 'load-styles.php'. Those scripts basically combine js >>> and css files into single large requests. I was seeing those files suddenly >>> coming through cut off, or having garbage characters thrown on the end (that >>> might have been from the browsers choking on them). Firefox and Safari were >>> being affected, Chrome wasn't having the issue. At first, I though it was a >>> gzip issue. But turning it off wasn't fully resolving the issue. What >>> stopped it was turning off 'Chunked Encoding' on the server connections. >>> Haven't seen the issue again after that. >>> >>> So is 'Chunked Encoding' know to be broken on 1.2.2, or could it be >>> causing issues in combination with some other problem I might have? >>> >>> Thanks >>> >>> >> ------------------------------ >> >> Tony Zakula <[email protected]> >> March 31, 2011 6:40 PM >> >> >> I've been running a Cherokee server on Ubuntu 10.10, with PHP 53 >>> serving Wordpress for the last 6 months or so. I've been keeping Cherokee up >>> to date pretty much since v0.9. >>> >>> But with 1.2.2, I'm having the Wordpress admin panel throwing errors with >>> 'load-scripts.php' and 'load-styles.php'. Those scripts basically combine js >>> and css files into single large requests. I was seeing those files suddenly >>> coming through cut off, or having garbage characters thrown on the end (that >>> might have been from the browsers choking on them). Firefox and Safari were >>> being affected, Chrome wasn't having the issue. At first, I though it was a >>> gzip issue. But turning it off wasn't fully resolving the issue. What >>> stopped it was turning off 'Chunked Encoding' on the server connections. >>> Haven't seen the issue again after that. >>> >>> So is 'Chunked Encoding' know to be broken on 1.2.2, or could it be >>> causing issues in combination with some other problem I might have? >>> >>> Thanks >>> >> >> Wow! Interesting. Were you by chance seeing these errors under https >> or http? >> >> Thanks! >> >> Tony Z >> _______________________________________________ >> Cherokee mailing list >> [email protected] >> http://lists.octality.com/listinfo/cherokee >> ------------------------------ >> >> Keith <[email protected]> >> March 31, 2011 3:01 PM >> >> I've been running a Cherokee server on Ubuntu 10.10, with PHP 53 serving >> Wordpress for the last 6 months or so. I've been keeping Cherokee up to date >> pretty much since v0.9. >> >> But with 1.2.2, I'm having the Wordpress admin panel throwing errors with >> 'load-scripts.php' and 'load-styles.php'. Those scripts basically combine js >> and css files into single large requests. I was seeing those files suddenly >> coming through cut off, or having garbage characters thrown on the end (that >> might have been from the browsers choking on them). Firefox and Safari were >> being affected, Chrome wasn't having the issue. At first, I though it was a >> gzip issue. But turning it off wasn't fully resolving the issue. What >> stopped it was turning off 'Chunked Encoding' on the server connections. >> Haven't seen the issue again after that. >> >> So is 'Chunked Encoding' know to be broken on 1.2.2, or could it be >> causing issues in combination with some other problem I might have? >> >> Thanks >> >> >
<<postbox-contact.jpg>>
<<image.jpg>>
<<image.jpg>>
<<compose-unknown-contact.jpg>>
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
