Yes, I can reproduce it but a bit different than described in the initial post. STR: 1. Enable https-only mode 2. Visit http://download.proxmox.com/debian/pve/dists/buster/pve-no-subscription/binary-amd64/ 3. After Exeception page is loaded, reload current page. 4. Now the user gets warned by firefox. The browser received an error (`SSL_ERROR_BAD_CERT_DOMAIN`). 5. Click on `Advanced` and then on `Accept Risk and continue`. 6. At this step the user gets asked for a login and if no login is provided an 401 error code occurs. There is some redirection problem.
Bug 1714661 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Yes, I can reproduce it but a bit different than described in the initial post. STR: 1. Enable https-only mode 2. Visit http://download.proxmox.com/debian/pve/dists/buster/pve-no-subscription/binary-amd64/ 3. After the exception page is loaded, reload current page. 4. Now the user gets warned by firefox. The browser received an error (`SSL_ERROR_BAD_CERT_DOMAIN`). 5. Click on `Advanced` and then on `Accept Risk and continue`. 6. At this step the user gets asked for a login and if no login is provided an 401 error code occurs. There is some redirection problem.
Yes, I can reproduce it but a bit different than described in the initial post. STR: 1. Enable https-only mode 2. Visit http://download.proxmox.com/debian/pve/dists/buster/pve-no-subscription/binary-amd64/ 3. After the exception page is loaded, reload current page. 4. Now the user gets warned by firefox. The browser received an error (`SSL_ERROR_BAD_CERT_DOMAIN`). 5. Click on `Advanced` and then on `Accept Risk and continue`. 6. At this step the user gets asked for a login and if no login is provided an 401 error code occurs. There is some redirection problem. Those steps can be done with every site (I tested so far) that isn't supporting https. Only the error code might be an 404 instead of an 401. I will investigate why it happens.
Yes, I can reproduce it but a bit different than described in the initial post. STR: 1. Enable https-only mode 2. Visit http://download.proxmox.com/debian/pve/dists/buster/pve-no-subscription/binary-amd64/ 3. After the exception page is loaded, reload current page. 4. Now the user gets warned by firefox. The browser received an error (`SSL_ERROR_BAD_CERT_DOMAIN`). 5. Click on `Advanced` and then on `Accept Risk and continue`. 6. At this step the user gets asked for a login and if no login is provided an 401 error code occurs. There is some redirection problem. Those steps can be done with every site (I tested so far) that isn't supporting https. Only the error code might be an 40x instead of an 401. I will investigate why it happens.
Yes, I can reproduce it but a bit different than described in the initial post. STR: 1. Enable https-only mode 2. Visit http://download.proxmox.com/debian/pve/dists/buster/pve-no-subscription/binary-amd64/ 3. After the exception page is loaded, reload current page. 4. Now the user gets warned by firefox. The browser received an error (`SSL_ERROR_BAD_CERT_DOMAIN`). 5. Click on `Advanced` and then on `Accept Risk and continue`. 6. At this step the user gets asked for a login and if no login is provided an 401 error code occurs. There is some redirection problem. Those steps can be done with every site (I tested so far) that isn't supporting https. Only the error code might be one of the 40x status codes. I will investigate why it happens.
Yes, I can reproduce it but a bit different than described in the initial post. STR: 1. Enable https-only mode 2. Visit http://download.proxmox.com/debian/pve/dists/buster/pve-no-subscription/binary-amd64/ 3. After the exception page is loaded, reload current page. 4. Now the user gets warned by firefox. The browser received an error (`SSL_ERROR_BAD_CERT_DOMAIN`). 5. Click on `Advanced` and then on `Accept Risk and continue`. 6. At this step the user gets asked for a login and if no login is provided an 401 error code occurs. There is some redirection problem. Those steps can be done with every site (I tested so far) that isn't supporting https. Only the error code might be a different one of the 40x status codes. I will investigate why it happens.