Closed Bug 736023 Opened 12 years ago Closed 12 years ago

Site with SPDY not reachable [nginx-devel-interop]

Categories

(Core :: Networking: HTTP, defect)

14 Branch
x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: m.tiefenbacher, Unassigned)

References

()

Details

(Whiteboard: [spdy])

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120314 Firefox/14.0a1
Build ID: 20120314130626

Steps to reproduce:

We (durchblicker.at) have an affiliate programm on an nginx server with spdy.
In firefox 11 with spdy enabled i can't reach the sites:
* https://partner.durchblicker.at/affiliates/panel.php
* https://partner.durchblicker.at/affiliates/signup.php

But this sites are reachable with spdy:
* https://partner.durchblicker.at/affiliates/indey.php
* https://partner.durchblicker.at/affiliates/faq.php

In google chrome i can reach all sites with spdy.


Actual results:

No response from the sites.


Expected results:

Site with Contact/Login form should appear.
Works correctly with disabled spdy and google chrome.
right URL: https://partner.durchblicker.at/affiliates/index.php (not indey.php)
Component: Untriaged → Networking
Product: Firefox → Core
QA Contact: untriaged → networking
Version: 11 Branch → 14 Branch
Markus, I think its awesome you're working on nginx for spdy. Please reach out to me directly for any help or testing I can do for you!

as for https://partner.durchblicker.at/affiliates/panel.php

generates this error (you need to turn on http logging to see it): "transfer-encoding found. Chunked is invalid and no TE sent."

The response headers are first a 302, and then after chasing the redirect they are:

HTTP/1.1 200 OK^M
date: Thu, 15 Mar 2012 13:20:29 GMT^M
server: Apache/2.2.15 (CentOS)^M
x-powered-by: PHP/5.3.3^M
expires: Thu, 19 Nov 1981 08:52:00 GMT^M
cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0^M
pragma: no-cache^M
set-cookie: A_pap_sid=7bhol17ljvlc5ehe2m4h7ac435; path=/^M
transfer-encoding: chunked^M
content-type: text/html; charset=UTF-8^M

Chunked encodings in spdy/2 are not valid. Please see "Chunked encoding is no longer valid." under "HTTP Layering over SPDY" in http://dev.chromium.org/spdy/spdy-protocol/spdy-protocol-draft2

Spdy v3 (which we don't yet speak), has the same policy.

further, your response body (the data segments) is not actually chunked encoded.

I'll try and get the chromium team to match this behavior.

https://partner.durchblicker.at/affiliates/signup.php has a similar problem.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Summary: Site with SPDY not reachable → Site with SPDY not reachable [nginx-devel-interop]
Whiteboard: [spdy]
Component: Networking → Networking: HTTP
QA Contact: networking → networking.http
chrome also plans to rst on this condition:

http://code.google.com/p/chromium/issues/detail?id=118398
thanks, we fixed the encoding problem!
You need to log in before you can comment on or make changes to this bug.