POSTToNonCanonicalURL error using bazaar client

I think this one is legit, but no idea why bzr would be posting to it.

I think the user ran 'bzr <something> https://launchpad.net/openerp-Medical%20<more stuff here that zope has cut off>'

Bzr will attempt to POST to that for the smart server support. The url bzr uses would be
https://launchpad.net/openerp-Medical%20<more stuff here that zope has cut off>/.bzr/smart

This isn't a bug per se, its user error, and I'd suggest not raising an error in zope when someone has tried to post to .../.bzr/smart.

Also, it shouldn't affect the user experience (though we might like to test that to be sure), so marking wishlist.

On Sat, 28 Nov 2009 01:07:51 Launchpad Bug Tracker wrote:
> You have been subscribed to a public bug:
>
> As seen in OOPS-1418K688 a POSTToNonCanonicalURL was raised when an user
> tried to POST to https://launchpad.net/openerp-Medical%20 using
> bzr/2.0.2 (urllib)

I believe this is a valid oops. I've contacted the bzr team to try to work
out why bzrlib would be posting to Launchpad URLs.

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

Tim Penhey wrote:
> On Sat, 28 Nov 2009 01:07:51 Launchpad Bug Tracker wrote:
>> You have been subscribed to a public bug:
>>
>> As seen in OOPS-1418K688 a POSTToNonCanonicalURL was raised when an user
>> tried to POST to https://launchpad.net/openerp-Medical%20 using
>> bzr/2.0.2 (urllib)
>
> I believe this is a valid oops. I've contacted the bzr team to try to work
> out why bzrlib would be posting to Launchpad URLs.

With an http URL, bzr always tries to determine whether a smart server
is present by POSTing to .bzr/smart. (nosmart+http:// disables this, I
believe)

Aaron

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

iEYEARECAAYFAksT3pYACgkQ0F+nu1YWqI3j8ACfVNd081WUuCFyyvpM8aqqtStb
384AoIEQBCG9GRK1fRnLXmeGOl5kTMTj
=0edv
-----END PGP SIGNATURE-----

According to the OOPS tool, the last time we saw this OOPS was July 14, 2010, at 10:19 p.m. We still use POSTToNonCanonicalURL in the codebase, so this looks like the problem has gone away one way or another.

I'm going to mark this Invalid. If anyone disagrees, it would be easy enough to handle that URL specially, so reopen it and say so.

https://lp-oops.canonical.com/oops/?oopsid=OOPS-0c0c5ff94cf9fa35380bbe42e07c9530

POSTToNonCanonicalURL:

    Traceback (most recent call last):
  Module zope.publisher.publish, line 131, in publish
    obj = request.traverse(obj)
  Module zope.publisher.browser, line 542, in traverse
    ob = super(BrowserRequest, self).traverse(obj)
  Module zope.publisher.http, line 455, in traverse
    ob = super(HTTPRequest, self).traverse(obj)
  Module zope.publisher.base, line 261, in traverse
    obj = publication.traverseName(self, obj, entry_name)
  Module zope.app.publication.zopepublication, line 197, in traverseName
    ob2 = adapter.publishTraverse(request, nm)
  Module lp.app.browser.launchpad, line 819, in publishTraverse
    return Navigation.publishTraverse(self, request, name)
  Module lp.services.webapp.publisher, line 854, in publishTraverse
    nextobj = self._publishTraverse(request, name)
  Module lp.services.webapp.publisher, line 1008, in _publishTraverse
    nextobj = self.traverse(name)
  Module lp.app.browser.launchpad, line 761, in traverse
    raise POSTToNonCanonicalURL
POSTToNonCanonicalURL

I reclosed the bug because this issue is about bzr doing improper behaviour. There are other cases when Lp will raise this and they need separate bugs for separate investigations. This is only an error is Lp does the POST. We will ignore hackers.