Bazaar fails with http transport on some servers

[Aaron Bentley]

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

Thomas Christensen wrote:
> I was asked by Stefan to investigate where is the bug: at savannah or
> in bzr.  What do you think?

I am inclined to think the bug is in Bazaar.

If they were returning 403 for a GET, that would be unreasonable-- they
shouldn't be choosing which files are permitted in .bzr.

However, a GET of
http://arch.sv.gnu.org/archives/emacs/bzr/emacs.app/.bzr/smart produces
a 404, as it should.

So it seems they're refusing the request because it is a POST request,
and this is their prerogative; Bazaar should not require POST in order
to fetch from plain http servers, just GET and HEAD.  Technically, they
should be replying with 405, IIUC.

I think Bazaar needs to accept a wide range of failures when determining
whether the smart server is supported.  At least 403, 404, 405, 410.
Possibly 500, 501, 503 as well (i.e. fallback to dumb operations if the
smart server is broken).   But when doing normal operations, it should
not use this broader list.

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

iD8DBQFIA63F0F+nu1YWqI0RAmVVAJ94Kw5S4wBRd4Ze+zivJlPpn5vgbwCfRrz6
yTRGzZrG4erELKc80NBje2E=
=ZDF2
-----END PGP SIGNATURE-----