Hi Carmen, Daisuke's on PTO for the next week (I am too after today) so I looked into this. Firefox is loading the correct URL, which is: https://www.mozilla.org/products/vpn?utm_medium=firefox-destkop&utm_source=firefox-suggest&utm_campaign=evergreen The server responds with a [302](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/302), which is a type of redirect. It actually responds with two 302's in a row, and then something (a script on the site probably) causes Firefox to load the final URL. I'm in the US not on a VPN, and based on your comment is sounds like the server redirects to different URLs depending on where you are. So Firefox is sending the right URL to the server. After that, it's up to the server to do whatever it wants to do with it. We may need to talk with the VPN/webdev teams to make sure they're handling the URL correctly, but from our POV (client engineering), this is fixed. Here's the full series of steps: 1. Firefox loads the original URL 2. The server responds with a 302 that redirects to the following path: `/en-US/products/vpn?utm_medium=firefox-destkop&utm_source=firefox-suggest&utm_campaign=evergreen` 3. Firefox loads that new path 4. The server responds with a 302 that redirects to the following path: `/en-US/products/vpn/` 5. Something (a script probably) causes Firefox to load the final path: `/en-US/products/vpn/?entrypoint_experiment=vpn-landing-bundle-promo&entrypoint_variation=c` If you want, you can verify this by opening the Network panel of Firefox's devtools. Check the Disable Cache checkbox, and click the gear icon and then check Persist Logs. Then click the trash can icon to clear the logs, paste the original URL into the urlbar, and hit enter.
Bug 1970867 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hi Carmen, Daisuke's on PTO for the next week (I am too after today) so I looked into this. Firefox is loading the correct URL, which is: https://www.mozilla.org/products/vpn?utm_medium=firefox-destkop&utm_source=firefox-suggest&utm_campaign=evergreen The server responds with a [302](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/302), which is a type of redirect. It actually responds with two 302's in a row, and then something (a script on the site probably) causes Firefox to load the final URL. I'm in the US not on a VPN, and based on your comment it sounds like the server redirects to different URLs depending on where you are. So Firefox is sending the right URL to the server. After that, it's up to the server to do whatever it wants to do with it. We may need to talk with the VPN/webdev teams to make sure they're handling the URL correctly, but from our POV (client engineering), this is fixed. Here's the full series of steps: 1. Firefox loads the original URL 2. The server responds with a 302 that redirects to the following path: `/en-US/products/vpn?utm_medium=firefox-destkop&utm_source=firefox-suggest&utm_campaign=evergreen` 3. Firefox loads that new path 4. The server responds with a 302 that redirects to the following path: `/en-US/products/vpn/` 5. Something (a script probably) causes Firefox to load the final path: `/en-US/products/vpn/?entrypoint_experiment=vpn-landing-bundle-promo&entrypoint_variation=c` If you want, you can verify this by opening the Network panel of Firefox's devtools. Check the Disable Cache checkbox, and click the gear icon and then check Persist Logs. Then click the trash can icon to clear the logs, paste the original URL into the urlbar, and hit enter.
Hi Carmen, Daisuke's on PTO for the next week (I am too after today) so I looked into this. Firefox is loading the correct URL, which is: https://www.mozilla.org/products/vpn?utm_medium=firefox-destkop&utm_source=firefox-suggest&utm_campaign=evergreen The server responds with a [302](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/302), which is a type of redirect. It actually responds with two 302's in a row, and then something (a script on the site probably) causes Firefox to load the final URL. I'm in the US not on a VPN, and based on your comment it sounds like the server redirects to different URLs depending on where you are. So Firefox is sending the right URL to the server. After that, it's up to the server to do whatever it wants to do with it. We may need to talk with the VPN/webdev teams to make sure they're handling the URL correctly, but from our POV (client engineering), this is fixed. Here's the full series of steps: 1. Firefox loads the original URL 2. The server responds with a 302 that redirects to the following path: `/en-US/products/vpn?utm_medium=firefox-destkop&utm_source=firefox-suggest&utm_campaign=evergreen` 3. Firefox loads that new path 4. The server responds with a 302 that redirects to the following path: `/en-US/products/vpn/` 5. Firefox loads that new path 6. Something (a script probably) causes Firefox to load the final path: `/en-US/products/vpn/?entrypoint_experiment=vpn-landing-bundle-promo&entrypoint_variation=c` If you want, you can verify this by opening the Network panel of Firefox's devtools. Check the Disable Cache checkbox, and click the gear icon and then check Persist Logs. Then click the trash can icon to clear the logs, paste the original URL into the urlbar, and hit enter.