Hi Fabien, I just came also across this issue. I guess this is a bug as the Chapter12 talks about HTTP1.1 support. Also it sees that some Browsers have issues with the Headers described in Chapter12 if you send HTTP1.0 instead of HTTP1.1.
So I would say: no this IS a bug. But I havent checked BC issues yet .: Fabian -----Original Message----- From: [EMAIL PROTECTED] om [mailto:[EMAIL PROTECTED] groups.com] On Behalf Of Fabien POTENCIER Sent: Freitag, 26. Oktober 2007 17:45 To: [email protected] Subject: [symfony-devs] Re: HTTP1.0 - why? I think we can change it for 1.1, not for 1.0. 1.0 branch is only for bug fixes and this is not a bug. You can also update the CHANGELOG file located at the root directory/ -- Fabien Potencier Sensio CEO - symfony lead developer http://www.sensiolabs.com/ http://www.symfony-project.com/ Sensio Labs Tél: +33 1 40 99 80 80 Ian P. Christian wrote: > Fabien POTENCIER wrote: >> I think we can commit this safely. > > I shall commit this to trunk (if applicable) and sf1.0.x for the next > release, is there a changelog that should be updated? this could give > potential performance improvements so much be worth mentioning > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
