shared repositories and 403 http servers
Bug #342119 reported by
Vincent Ladeuil
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
As encountered at https:/
As discussed with lifelees, we could relax the definition of repository.
Changed in bzr: | |
assignee: | nobody → vila |
status: | New → In Progress |
importance: | Undecided → Low |
tags: | added: check-for-breezy |
To post a comment you must log in.
A bit of feedback here: I first thought this can be easily addressed without changing the contract which is that the boolean to decide if a repository is shared is implemented by the existence of a file.
It turns out (trying to write the tests made that clear) that interpreting a 403 forbidden error as the absence of a file is too large and can't be simply addressed at the http transport level (i.e. make it a special case for http only).
Since this is arguably a server configuration problem and that there is a possible work around (make the repository shared even for a single branch), I think there is no urgency to fix that bug and that we should change the contract instead and find another implementation for shared repository property (which is a more invasive change and requires a format bump).