Bonjour,
There is an easy way to workaround this issue: disable the RangeService for
your application.
I've also added a link back to your report in issue 651. With the increasing
usage of partial request (HTML 5 video streaming for example), we really need
to support multi-range requests.
Hi all,
The header request of FF3.6.3 contains a range and if-range header that
apparently causes an error with restlet 2.0m7 and the ultimate snapshot too:
FF generates call http get and on the second Restlet returns a '501 not
implemented error (returning a FileRepresentation of a PDF file).
well, I can't really get around ... some times it works (null-ing range tag)
.. some times not
don't understand ...
help?
thanks
--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/Restlet-and-FF-in-Windows-range-out-of-range-NEW-tp5136708p5136817.html
Sent from
how can I know if this is a adobe plugin problem with restlet ?
is this the Issue 651 ?
I thought it was corrected.
--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/Restlet-and-FF-in-Windows-range-out-of-range-NEW-tp5136708p5136831.html
Sent from the Restlet
well this is th adobe plugin / restlet relationship that causes this error.
so this is Issue 651.
is there a good way to get around ?
--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/Restlet-and-FF-in-Windows-range-out-of-range-NEW-tp5136708p5136876.html
Sent
5 matches
Mail list logo