[TYPO3-english] TYPO3 6.2 and content length mismatch error

[Nicola Cerchiari]

​Hi Markus,
you're surely right and as soon as I'll have time to investigate it I will.

"Solved" was more a "I found a way to make it work for now, please don't
bother yourself to ​try to find a solution or clues for me" :-).
Noww with time I'll dig into it.

Bests,
Nicola


2014-03-31 19:55 GMT+02:00 Markus Klein <klein.t3 at mfc-linz.at>:

> Hi!
>
> I would not call that a solution.
> You just disabled sending the header. ^^
>
> A solution would be a correct length output or a reason why the mobile
> device gets more data than the header suggests.
>
> Kind regards
> Markus
>
> ------------------------------------------------------------
> Markus Klein
> TYPO3 CMS Active Contributors Team Member
>
> >
> > SOLVED! I'll answer myself quoting "when something loks too complicated
> to
> > be solved the solution is of course the easiest one".
> > The big problem was generated by the new default (
> > http://forge.typo3.org/issues/50483) of the setting:
> >
> > config.enableContentLengthHeader
> >
> > ​Setting it to 0 solves the problem.
> >
> > Thanks anyways,
> > Nicola​
> >
> >
> >
> >
> > 2014-03-31 18:02 GMT+02:00 Nicola Cerchiari <nicola.cerchiari at gmail.com
> >:
> >
> > > Hi all,
> > > I just published a very simple website made with the brand new TYPO3
> > > 6.2 and the common fluidtypo3/fedext setup (fluidpages, fluidcontent,
> > > vhs, ...).
> > > Everything went flawless until today when I deployed the website on
> > > the hosting server.
> > > To make it short if I try to surf the website from mobile I only get
> > > the
> > > error:
> > > net::ERR_CONTENT_LENGTH_MISMATCH
> > >
> > > ​The only mobile browser that seems not to care is Chrome even if
> > > emulating mobile on desktop clearly shows the error in the dev tools
> > > (the strange thing is that on desktop mode there no error at all).​
> > >
> > >
> > > ​I checked also with w3c validator for any mistake in developing the
> > > templates, but nothing.
> > >
> > > The provider told me that they could not reproduce the error no matter
> > > what devices they used (they tried with some iPhones and Android).
> > >
> > >
> > > ​Anyone has any idea abut this issue? I'm really ruuning out of them.
> > > If you need any other info to better understand please don't hesitate.
> > >
> > > Thanks in advance to everyone​
> > >
> > >
> > > --
> > > *Nicola Cerchiari*
> > > _______________________________________________
> > > TYPO3-english mailing list
> > > TYPO3-english at lists.typo3.org
> > > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
> >
> >
> >
> >
> > --
> > *Nicola Cerchiari*
> > _______________________________________________
> > TYPO3-english mailing list
> > TYPO3-english at lists.typo3.org
> > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english




-- 
*Nicola Cerchiari*