ERR_SPDY_PROTOCOL_ERROR when enabling SPDY
Hi ! I use BIG-IP 11.6.0 and try to enable SPDY. I have a VS with an Access Policy that uses an 'External Logon Page' action. My config: ifile with a custom login page VS with: No Client SSL profile An AP that starts with an 'External Logon Page' action with a Server URI '/login' A pool select irule used to direct traffic to the login ifile : switch -regexp -- [string tolower [HTTP::path]] { "^/login(/|$)" { HTTP::respond 200 content [ifile get login-form] ... } ... (pool selects for actual services) ... } In front of this VS I have another VS. It has a Client SSL profile Without SPDY When I don't have SPDY enabled on my front VS everything works: /myservice 302 -> /my.policy 200 OK (APM will initiate a POST to the external logon page, /login) /login 200 OK. (/login is an iFile) user enters credentials (/login POST's these to /my.policy) -> /my.policy 302 -> /myservice (and I'm logged in) With SPDY When I enable SPDY on the front VS, things break: /myservice 302 -> /my.policy 200 OK (APM will initiate a POST to the external logon page, /login) /login ( This request is made, but bad/no response is received by the client) Chrome shows 'not available, ERR_SPDY_PROTOCOL_ERROR'. dev tool shows 'CAUTION: Provisional headers are shown' in place of request headers. No reponse headers are shown FF shows 'Secure Connection Failed' IE works In the ltm log I can see: the AP in the inner VS has started the /login ifile has been served the outer VS has fired a HTTP_RESPONSE event There are no log entries in apm or ltm other than those i make myself if I go directly to the custom login page (i.e. https://mysite.no/login) I get the same error. If I repeat the request for the custom login page, it works (!) I make no other change than enabling SPDY. If I disable SPDY again everything works normally. Any tips on how to figure out this issue? I find nothing in the BIG-IP logs, error messages from the browsers are very generic, and since SPDY only works over HTTPS listening in on the traffic is difficult.307Views0likes0Comments11.6.0 SPDY Connection from iOS 8
Sorry to make this so generic, but has anybody seen an iOS 8 device successfully connect to a SPDY enabled virtual server on 11.6.0? I've tried applying /Common/spdy under both HF1 and HF3, and iOS devices stop being able to connect. Wireshark shows rapid connection attempts until the user cancels. Safari on Yosemite also seems unhappy, but every other browser functions correctly and the statistics show plenty of SPDY requests happening. Thanks for any sanity check you can offer.314Views0likes4CommentsSPDY and Web Acceleration cannot be used together
If I enable both a SPDY and Web Acceleration profile on a Virtual Server, the initial html page is downloaded but all subsequent HTTP requests (javascript, css, images etc.) return with size 0 and response status 0. If I switch off either of them then it seems to work fine. Has anyone else encountered this? Platform: BIG-IP 11.5.0 Build 1.0.227 Hotfix HF1298Views0likes2CommentsSPDY not working with Chrome browser on Android
Hi, we're experimenting with SPDY profiles on LTM 11.4 SPDY seems to be working fine with spdy-enabled desktop browsers (Chrome, Firefox) and also with non-spdy browsers (IE, iPhone?) The only browser, which can't get a connection to an spdy-enabled virtual server is Google Chrome on Android. There we get "ERR_CONNECTION_CLOSED" on the client. On a tcpdump, the SSL-handshake seems ok, but then the loadbalancer ends the connection (FIN). Might be a browser bug (though since Google invented SPDY, one would think SPDY on Google Chrome should be flawless). Has anybody experienced the same, has any hints or can at least confirm this? LTM: 11.4.1 Browser: Android Chrome 35.0.1916.138 Thank you in advance, Markus499Views0likes4CommentsLTM SPDY Passthru
hi everyone, we have an apache server configured to support the SPDY protocol. we accessing the website directly, SPDY seems to working just fine. when accessing the site via LTM, SPDY doesnt work, even when SPDY profile is enabled. is there a way to have the LTM just pass SPDY request to a supporting server rather than using it as a proxy? we are on version 11.3.0 HF6 thanks in advance.219Views0likes1Comment