Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

HTTP 307 with Authorization Header not redirecting, same thing works in chrome?

  • 2 odgovora
  • 1 ima ovaj problem
  • 6 prikaza
  • Posljednji odgovor od cor-el

more options

Firefox with AWS API Gateway returning a 307 redirection is not working. The API gateway is configured to use Cognito and so the GET request HTTP header is set with "Authorization" and all the servers both AWS and the redirection server is configured to return response with Access-Control-Allow-Origin: * Firefox is not showing the redirection URL request in the web developer. Also tried in safe mode didn't worked there also. Same website works fine in Google chrome and the 307 is redirected to the one specified in the location header and the same Authorization header is both send to AWS and to the redirected URL.

Firefox with AWS API Gateway returning a 307 redirection is not working. The API gateway is configured to use Cognito and so the GET request HTTP header is set with "Authorization" and all the servers both AWS and the redirection server is configured to return response with Access-Control-Allow-Origin: * Firefox is not showing the redirection URL request in the web developer. Also tried in safe mode didn't worked there also. Same website works fine in Google chrome and the 307 is redirected to the one specified in the location header and the same Authorization header is both send to AWS and to the redirected URL.

Svi odgovori (2)

more options

Sounds more like a site issue.

more options