Auto-populating Bugzilla link is not https

VERIFIED FIXED in 2.4.4

Status

VERIFIED FIXED
7 years ago
7 years ago

People

(Reporter: zcampbell, Assigned: espressive)

Tracking

Trunk
2.4.4
x86_64
Windows 7

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
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

To avoid the redirect and correctly represent the final destination we should provide the link with https.
(Assignee)

Comment 1

7 years ago
Sent pull request :: https://github.com/mozilla/socorro/pull/364

TEST CASE
----------

When encountering an error or not found page the link through to Bugzilla has a bug_file_loc parameter. The value of this parameter is the current URL and the protocol should always match the protocol the page is be server via.

So if the page is https it should be https in bug_file_loc and vice versa.
Assignee: nobody → sneethling
Target Milestone: --- → 2.4.4
(Assignee)

Updated

7 years ago
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED

Comment 2

7 years ago
Commit pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/ee3b292a226f6e6cfaeeb72ce14e3dd538311c79
ensure that bug_file_loc always uses the correct protocol fixes bug 715202

Comment 3

7 years ago
Commits pushed to jberkus-master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/277ebbbacb6f8a7f9692090e1b0c06e27deb6d14
ensure that bug_file_loc always uses the correct protocol fixes bug 715202

https://github.com/mozilla/socorro/commit/b97ba64c14291f96634b96b08b3722a9f8415da1
Merge pull request #364 from ossreleasefeed/bugzilla-link-not-https-715202

ensure that bug_file_loc always uses the correct protocol fixes bug 715202
QA verified on prod. Good find zac.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.