Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Den här webbplatsen har begränsad funktionalitet medan vi utför underhåll för att förbättra din upplevelse. Om en artikel inte löser ditt problem och du vill ställa en fråga har vi vår gemenskap som väntar på att hjälpa dig på @FirefoxSupport på Twitter, /r/firefox på Reddit.

Avatar for Username

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Denna tråd har arkiverats. Ställ en ny fråga om du behöver hjälp.

Firefox isn't redirecting when it gets a HTTP 302

  • 7 svar
  • 10 har detta problem
  • 1 visning
  • Senaste svar av cor-el

movzillamws
movzillamws
more options

After filling out a simple form on this page: https://bitdango.com/register/email

The page should redirect to this page: https://bitdango.com/register/verify

Instead nothing happens. The browser simply doesn't redirect.

I have tried both relative and fully qualified URLs in the "Location" property of the redirect, neither are working.

Why is the browser not redirecting? Users are starting to use Chrome instead of Firefox because of this.

After filling out a simple form on this page: https://bitdango.com/register/email The page should redirect to this page: https://bitdango.com/register/verify Instead nothing happens. The browser simply doesn't redirect. I have tried both relative and fully qualified URLs in the "Location" property of the redirect, neither are working. Why is the browser not redirecting? Users are starting to use Chrome instead of Firefox because of this.

Vald lösning

Glad you resolved the problem. More on SPDY at https://en.wikipedia.org/wiki/SPDY .

To avoid other people encountering this problem, I suggest you report this as a bug through https://bugzilla.mozilla.org/.

Läs svaret i sitt sammanhang 👍 0

Alla svar (7)

user1027088
user1027088
more options

For info, it just worked for me, redirecting me to the relevant page. I'm using Firefox 26.0.

movzillamws
movzillamws Frågans ägare
more options

It seems to work half the time. It is not consistent, which is making it hard to troubleshoot.

Half the time the call to: https://bitdango.com/register/verify

works and the other 1/2 the time it doesn't work. When it doesn't work no response is shown in the "Network" section of the debug tool. When it does work I see a HTTP Header that I wonder about:

X-Firefox-Spdy: "2"

Not sure if that has anything to do with it?

user1027088
user1027088
more options

Have you tried using an external network debug tool such as the free Fiddler? That will allow you to see the HTTP traffic associated with your browsing and may shed some light.

movzillamws
movzillamws Frågans ägare
more options

So I changed the network.http.spdy.enabled from true to false. Now redirects are working as expected.

Need to learn more about what SPDY is and expectations for working with websites, etc...

user1027088
user1027088
more options

Vald lösning

Glad you resolved the problem. More on SPDY at https://en.wikipedia.org/wiki/SPDY .

To avoid other people encountering this problem, I suggest you report this as a bug through https://bugzilla.mozilla.org/.

user1027088
user1027088
more options

Additional info: although the redirection worked for me, I have network.http.spdy.enabled set to true.

Full settings:

network.http.spdy.allow-push;true network.http.spdy.chunk-size;4096 network.http.spdy.coalesce-hostnames;true network.http.spdy.enabled;true network.http.spdy.enabled.v2;true network.http.spdy.enabled.v3;true network.http.spdy.persistent-settings;false network.http.spdy.ping-threshold;58 network.http.spdy.ping-timeout;8 network.http.spdy.push-allowance;65536 network.http.spdy.send-buffer-size;131072 network.http.spdy.timeout;180

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

I get this response headers: 

HTTP/1.1 302 OK
Server: nginx
Date: Mon, 30 Dec 2013 14:03:17 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 133
Cache-Control: private
Location: /register/verify
X-Firefox-Spdy: 2

Note that the X-Firefox-Spdy header is an entry that is generated by Firefox to show whether SPDY and which version was used, so it isn't send by the server.

Is it possible that there was another problem (e.g. the CAPTCHA) that prevented the redirect.