550502 - If ssl is set to always, and both sslbase and urlbase are set to https://url/to/bugzilla bugzilla creates a redirect loop

Status: RESOLVED INVALID

(Bugzilla :: Administration, task)

Description

[Lee Burton]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.249.43 Safari/532.5
Build Identifier: 

If ssl is set to always, and both sslbase and urlbase are set to https://url/to/bugzilla bugzilla creates a redirect loop.
Bugzilla tries to redirect to https://www/bugs to https://www/bugs.  This little error could easily be solved by checking if there is "https://" at the start of urlbase when ssl is set... setting ssl to never fixes it.

Reproducible: Always

Steps to Reproduce:
1. set both sslbase and urlbase to the same https addy
2. set ssl to always
3. watch the loop in your web browser
Actual Results:  
A loop.

Expected Results:  
Display my https'd page.

setting ssl to never fixes it.

Comment 1

[Frédéric Buclin]

Which version of Bugzilla do you use?

Comment 2

[Max Kanat-Alexander]

  Bugzilla does not allow urlbase to be set to https:.

Comment 3

[Frédéric Buclin]

Maybe we should enforce this check in the validator when updating the urlbase parameter.

Comment 4

[Max Kanat-Alexander]

  We do. He had to hack Bugzilla or manually edit data/params to set it to https.

Comment 5

[Gunter Ohrner]

(In reply to Max Kanat-Alexander from comment #4)

We do. He had to hack Bugzilla or manually edit data/params to set it to
https.

This is not true, at least not in such a general way.

No idea which Bugzilla version Lee used back then, 11 years ago, but in Bugzilla 4.0.1 at least - which is more recent - it is entirely possible to set the urlbase to an https address, and I just accidentally created such an endless loop.