Forum Discussion

Sunkwan_Kim_147's avatar
Sunkwan_Kim_147
Icon for Nimbostratus rankNimbostratus
Jan 06, 2015

Doesn't Firefox support the Next-Protocol-Negotiation?

Hi all,

 

I am testing the SPDY Gateway with F5 TMOS 11.6.0 HF3 and Firefox 27. When I request the test webpage through HTTP, in the Chrome browser, I can see the response header 'Alternate-protocol : 443:npn-spdy/3.1' and Firefox too. It seems that the Chrome works well but the Firefox is not. The Firefox doesn't support the NPN? But in case, through the 443(HTTPS) Virtual Server, Firefox works well like Chrome.

 

Help me. Thanks.

 

application delivery
availability
deployment
devops
iRules
LTM
TMOS

3 Replies

Sort By
  • boneyard's avatar
    boneyard
    Icon for MVP rankMVP
    Jan 08, 2015
    for me it is unclear what does and doesn't work. could you make that more clear? as for you firefox question i would advise the firefox support forum.
  • Sunkwan_Kim_147's avatar
    Sunkwan_Kim_147
    Icon for Nimbostratus rankNimbostratus
    Jan 11, 2015
    When the client request the Web Page through the 80 VS, the client receives the npn-spdy header value by iRule. chrome users are redirected to 443 VS(SPDY profile is applied) BUT, firefox users are not.
  • Brad_Parker's avatar
    Brad_Parker
    Icon for Cirrus rankCirrus
    Jan 13, 2015

    Firefox does support SPDY and there is even a plugin to tell you when it is being used. As for why Chrome redirects to https when it sees the 'Alternate-protocol : 443:npn-spdy/3.1' header when received from an HTTP server that is probably because Google invented SPDY. I would recommend that your HTTP site issue a 301 to HTTPS and enable SPDY on the HTTPS virtual server.