Closed
Bug 732419
Opened 14 years ago
Closed 14 years ago
Expose only the domain specific urls for attachments
Categories
(Bugzilla :: Attachments & Requests, enhancement)
Bugzilla
Attachments & Requests
Tracking
()
RESOLVED
DUPLICATE
of bug 148562
People
(Reporter: bc, Unassigned)
Details
Background:
Attachments are exposed directly in bugzilla without the bug specific domain. e.g. https://bugzilla.mozilla.org?attachment.cgi?id=xxxx
When we load them or copy the url, we get this original non-bug specific url. But when we load the attachment, bugzilla then does a 302 found redirection to https://bug999999.bugzilla.mozilla.org/attachment.cgi?id=xxxx
Many times I find a references to an attachment url for a crash test case where it is awkward to determine the bug to which the attachment belongs without inadvertently crashing.
Enhancement request:
Instead of exposing the non-bug specific url for an attachment in bugzilla, we should instead just expose the bug specific url https://bug999999.bugzilla.mozilla.org/attachment.cgi?id=xxxx so that we don't need to do the redirect and can always easily identify the bug to which an attachment belongs without attempting to load it in some form.
Comment 1•14 years ago
|
||
Unfortunately with our current architecture this isn't likely to be possible--at least not in the case of security bugs. We hit attachment.cgi to get a token that authenticates your access and then we do a redirect. We can't expose that token anywhere else; that would allow unauthorized access to the attachment.
bc isn't asking for the full url, just that we use the attachhost prefix.
Comment 3•14 years ago
|
||
We won't use the attachmentbase url in the attachment table because Bugzilla would need to do redirection twice for private attachments and bugs, see mkanat's comment 1. So this part is wontfix. The difficulty to determine the bug ID when you know the attachment ID is already discussed in bug 148562.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•