Incorrect read length, http and php

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Allouche wrote:
> Aaron Bentley wrote:
>> I can kind of see how this might make sense if you're serving multiple
>> languages statically, and designing Apache to serve documents, not
>> files.  But personally, I'd write it so that it stopped at the first
>> unrecognized extension.
> 
> The fact is there are Apache servers out there, set up by competent
> sysadmins, that will cause bzr to blow chunks and die. People will not
> be able to diagnose it, and will conclude that bzr is buggy and
> unusable. Or at the very least that the much-vaunted dumb server support
> just isn't functional.
> 
> The only way out I see is adding a level of indirection, make the knit
> file names be arbitrary and independent of the file id.
> 
> That also has the benefit of sidestepping filesystem limitations when
> dealing with long file ids, especially if they contain mainy characters
> which are not lowercase ascii (then the urlencoding increases length of
> id-based file names even further).

The other alternative I can see is to design an escaping mechanism that
takes into accound what we have learned so far-- i.e., doesn't use
periods, percent signs or capital letters.

I'm not sure which approach I prefer at the moment.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFMkp70F+nu1YWqI0RAtAiAJsFcwG8kVUm8cWNty2i5Gybn9DB+ACfaTJU
AQ2w/460zQ64GYqBl45v5KI=
=MRWe
-----END PGP SIGNATURE-----