HTTP not working: Error 332 (net::ERR_SYN_REPLY_NOT_RECEIVED) about node-spdyproxy HOT 9 CLOSED

An older version of node-spdyproxy (from April) does not have these issues.

Here is the shrinkwrap output from the current version:

cat npm-shrinkwrap.json 
{
  "name": "spdyproxy",
  "version": "0.2.4",
  "dependencies": {
    "spdy": {
      "version": "1.5.0",
      "from": "spdy@~ 1.5"
    },
    "radius": {
      "version": "0.1.5",
      "from": "radius@~ 0.1"
    },
    "optimist": {
      "version": "0.3.7",
      "from": "optimist@~ 0.3.5",
      "dependencies": {
        "wordwrap": {
          "version": "0.0.2",
          "from": "wordwrap@~0.0.2"
        }
      }
    },
    "colors": {
      "version": "0.6.0-1",
      "from": "colors@*"
    },
    "memory-cache": {
      "version": "0.0.5",
      "from": "memory-cache@*"
    }
  }
}

from node-spdyproxy.

Interesting. I believe I just fixed the opposite bug (HTTPS not working - #29).. and I can't reproduce this case - both HTTP and HTTPS sites load fine for me, with latest node (0.10.8) and patched node-spdy.

from node-spdyproxy.

I also get this problem frequently, not never succeeded to reproduce it on localhost.

from node-spdyproxy.

I tried using the latest node-spdy 1.8.9 (in hope spdy-http2/node-spdy#95 might somehow magically fix the problem), but unfortunately I still get the aforementioned error (on localhost as well on 3 remote hosts)

HTTPS works perfectly though. :)

Is there anymore useful debug output that I can provide?
I'll try to play a bit more with different code / dependency versions in order to boil down the problem.

from node-spdyproxy.

FYI,

in chromium source code, the definition is very weird,

/net/spdy/spdy_session.cc

1519 if (stream->response_received()) {
1520 stream->LogStreamError(ERR_SYN_REPLY_NOT_RECEIVED,
1521 "Received duplicate SYN_REPLY for stream.");
1522 RecordProtocolErrorHistogram(PROTOCOL_ERROR_SYN_REPLY_NOT_RECEIVED);
1523 CloseStream(stream->stream_id(), ERR_SPDY_PROTOCOL_ERROR);
1524 return;
1525 }

The explanation is actually duplicated SYN_REPLY instead of missing SYN_REPLY.

@berstend Are you using any particular authHandler?

from node-spdyproxy.

Which version of Chrome are you on?

On Tue, May 28, 2013 at 12:57 PM, Duan Lian [email protected]:

FYI,

in chromium source code, the definition is very weird,

/net/spdy/spdy_session.cc

1519 if (stream->response_received()) {
1520 stream->LogStreamError(ERR_SYN_REPLY_NOT_RECEIVED,
1521 "Received duplicate SYN_REPLY for stream.");
1522 RecordProtocolErrorHistogram(PROTOCOL_ERROR_SYN_REPLY_NOT_RECEIVED);
1523 CloseStream(stream->stream_id(), ERR_SPDY_PROTOCOL_ERROR);
1524 return;
1525 }

The explanation is actually duplicated SYN_REPLY instead of missing
SYN_REPLY.

@berstend https://github.com/berstend Are you using any particular
authHandler?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/29#issuecomment-18575742
.

from node-spdyproxy.

@chemhack
In my chrome extension that updated the proxy settings I had a listener active that took care of entering user/pass credentials using this: chrome.webRequest.onAuthRequired.addListener.

At first, I thought that was the source of my issues: I removed the listener and the Proxy Authorization dialog appeared, I entered the credentials and was able to use HTTP sites (using local and remote node-spdyproxy instances).
Unfortunately that didn't last very long, the crude 332 error reappeared for good after a while and no more auth dialogs (even when restarting chrome).

I still have the feeling the error might be related to the auth part: While the Proxy Authorization dialog was open I got the 332 on all other tabs until I submitted the credentials.

@igrigorik
I'm using Chrome 26.0.1410.63 on x64 Ubuntu.
edit, the same issues also happen on a second machine (OSX; Chrome 27.0.1453.93).

from node-spdyproxy.

When using node-spdyproxy without authentication I have no issues at all.
All issues are related to using the proxy with Basic-Auth proxy authentication. :)

from node-spdyproxy.

@igrigorik It was introduced here mirror/chromium@fce44a0

long time ago really. The original error message was "Received duplicate SYN_REPLY for stream". But no idea why it was labeled as "ERR_SYN_REPLY_NOT_RECEIVED". So misleading.

from node-spdyproxy.