0.2.6 returning error: typeError: Cannot read property 'id' of undefined
Closed this issue · 5 comments
Proxying requests through spdyproxy returns "error: typeError: Cannot read property 'id' of undefined"
Chrome version 30
Nodejs version 0.10.20
Doh. Do you have a specific site that triggers it?
I think it is triggered by any site I visit when proxying through spdyproxy.
Could there be something wrong with my configuration?
I'm running the browser and node js with spdy proxy on the same machine running Windows 7.
The proxy I am using a self signed rsa certificate and key pair.
I'm using Chrome 30 with spdy enabled. Removing the pac config, i'm able to directly access spdy enabled websites. Here are my flags:
chrome.exe --enable-benchmarking --enable-net-benchmarking --enable-stats-table --proxy-pac-url="file:///C:/Users/Kev/Desktop/spdy.js" --enable-npn --use-spdy=npn --ignore-certificate-errors
Here's my typical setup:
$> bin/spdyproxy -k keys/mykey.pem -c keys/mycert.pem -p 44300 -v
$> "/Applications/Google Chrome Canary.app/Contents/MacOS/Google Chrome Canary" --proxy-pac-url=file:///git/spdyproxy/pac/secure-browsing.pac
Note that secure-browsing.pac is checked in, and I'm running spdyproxy right from the repo. Can you try checking out the master, running "npm install", and repeating the test?
It worked, thanks Ilya. I had to also append the --ignore-certificate-errors flag. I think the problem is caused by the --use-spdy=npn flag.
hi, i'm having the same issue, but only happens once at the beginning.
Chrome 32.0.1700.107, Node v0.10.18, spdyproxy (v. 0.2.6). I'm running OS X 10.9.1
$> spdyproxy -k ../keys/mykey.pem -c ../keys/mycert.pem -p 44300 -v
$> "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --proxy-pac-url=file:///Users/maxi/Documents/UNLu/Tesis/node_modules/spdyproxy/pac/secure-browsing.pac
i tried cloning the repo, and with "npm install". In both cases this happens.
In the previous version (v. 0.2.5) this doesn't happen.