User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

Entered a URL to an API which redirects the browser to an Angular application. Angular app calls back an endpoint on the API system and sends a UUID as an API key so that the back end API can identify the initial request.

Actual results:

Initial re-direct occurs correctly however the Angular application callback sends a blank value in the API key http header instead of the UUID value so the original request cannot be identified. Check the value for 'apikey' in the attached screen grab.

Expected results:

Testing with Firefox regular edition and Chrome it operates correctly in that the API key UUID is transmitted back to the API endpoint.

Hi Rich,

Thanks for reporting this bug.

Could you provide us with step by step instructions so we can try to reproduce it on our end?

As a starting point, I'll add a product and component to this ticket. Feel free to change it for a more appropriate one.

Regards,

Hi Virginia

Here are some instructions:-

1. Start FF Dev Edition

2. Open console

3. Load http://itg-angular.easychange.com/#/home - this Angular page will make several GET and OPTIONS XHR calls to an API endpoint

4. In the console - examine the Request headers of any GET XHR request and the parameter with the label 'apikey' will be empty

5. Start FF Standard edition or Chrome

6. Repeat steps 2 - 4 - you will see the Request parameter has the API key set to a GUID

The lack of the API key value from FF Dev Edition requests is causing issues for the API code

I can email you screen grabs if you need them

Hope that helps
Rich

Trying to get this closer to the right component.

Hello Rich,
Here's my testing result:
Firefox (Release) 69: empty
Firefox Dev 70: empty
Firefox Nightly 71: UUID

(a) What is the version of your workable FF? Is it 69?
(b) Could you verify if it's resolved in Nightly?

On the other hands, custom header isn't the best practice for sending the key.
It might be filtered by CDN, proxy, etc.

Hello

Answering your questions:-

a) FF v 56.0.2

b) It is not resolved (apikey header is still empty) in Nightly 71.0a1 (2019-09-27) (64-bit)

Regards
Rich

Since it works for previous Firefox builds (56.0.2 and before).
It would be very helpful if you could find the exact regression range.
https://mozilla.github.io/mozregression/quickstart.html

Could you help us please?
Thanks!

Unfortunately - I am struggling to install your mozregression tool on my development laptop (Mac OS X) the issue is not with your tool but it's with getting pip installed as it required a later version of OpenSSL than installed on my laptop and when I upgraded that it brought down Apache and PHP .... upshot is that I can't risk more downtime on my main development machine at the moment.

If I get some time then I will try and bisect on an Ubuntu container.

Please however continue your investigations nevertheless

Thanks