631737 - Add dynamic, auto-populating Bugzilla link from 404 page in Kohana

Status: RESOLVED FIXED

(Socorro :: General, task)

Description

[Stephen Donner [:stephend] Not actively reading bugmail]

The link to auto-populate a few Bugzilla fields from bug 630557 could also pre-populate the URL field, if you just tack on the current page as a param, like so:

&bug_file_loc=http%3A%2F%2Fsome_url

Full URL would be: https://bugzilla.mozilla.org/enter_bug.cgi?product=Webtools&component=Socorro&bug_file_loc=someurl

(This is assuming you can get some_url (the current page, which is 404'ing) from Kohana, which I think is possible.)

Comment 1

[Brandon Savage [:brandon]]

Attachment: Adding URL to 404

Grabbing the script URI as a second argument for Bugzilla.

Comment 2

[Brandon Savage [:brandon]]

Attachment: Less expansive patch

The first patch was too expansive for this specific bug.

Comment 3

[Brandon Savage [:brandon]]

Fixed in revision 3063 with the patch approved.

Comment 4

[Stephen Donner [:stephend] Not actively reading bugmail]

Verified FIXED on https://crash-stats.stage.mozilla.com/topcrasher/byversion/Firefox/4.0b13prefoo:

[08:42:53.000] GET https://crash-stats.stage.mozilla.com/topcrasher/byversion/Firefox/4.0b13prefoo [HTTP/1.1 404 File Not Found 73ms]
--
[08:43:07.035] GET https://bugzilla.mozilla.org/enter_bug.cgi?product=Webtools&component=Socorro&bug_file_loc=http%3A%2F%2Fcrash-stats.stage.mozilla.com%2Ftopcrasher%2Fbyversion%2FFirefox%2F4.0b13prefoo [HTTP/1.1 200 OK 820ms]

resulting field in Bugzilla was "http://crash-stats.stage.mozilla.com/topcrasher/byversion/Firefox/4.0b13prefoo".

Comment 5

[Zac C (:zac)]

Reopening this because the bugzilla url parameter does not contain HTTPS which is the standard protocol for Socorro.

Actual: bug_file_loc=http://crash-stats-dev.allizom.org/invaliddomain

Expected: bug_file_loc=https://crash-stats-dev.allizom.org/invaliddomain

Comment 6

[Brandon Savage [:brandon]]

This is using the built in server-generated URL. Since Apache will automatically redirect a user to HTTPS if necessary, this doesn't present a security problem. Since this bug has already been released, I'm closing as resolved-fixed but the person who reopened it should feel free to file a new bug if they feel there is still merit to this issue.