angularjs - Chrome is closing my ajax post at exactly 60 seconds -


i submitting information takes longer 60 seconds process, reason chrome closing connection @ 1 minute. have page cached akamai timeout 120 seconds, else must causing problem. don't have timeouts in our angular code or anywhere close. here output chrome's net internals. happens in chrome, ie , firefox process submit fine.

t=191705 [st=    0] +request_alive  [dt=60081] t=191705 [st=    0]    url_request_delegate  [dt=0] t=191705 [st=    0]   +url_request_start_job  [dt=60080]                        --> load_flags = 672000 (bypass_data_reduction_proxy | maybe_user_gesture | report_raw_headers | verify_ev_cert)                        --> method = "post"                        --> priority = "low"                        --> upload_id = "0"                        --> url = "https://qa2.web.com/payment/submit" t=191705 [st=    0]      url_request_delegate  [dt=0] t=191706 [st=    1]      http_cache_get_backend  [dt=0] t=191706 [st=    1]      url_request_delegate  [dt=0] t=191706 [st=    1]     +http_stream_request  [dt=0] t=191706 [st=    1]        http_stream_request_bound_to_job                            --> source_dependency = 4578 (http_stream_job) t=191706 [st=    1]     -http_stream_request t=191706 [st=    1]     +http_transaction_send_request  [dt=0] t=191706 [st=    1]        http_transaction_http2_send_request_headers                            --> :host: qa2.web.com                                :method: post                                :path: /payment/submit                                :scheme: https                                :version: http/1.1                                accept: application/json, text/plain, */*                                accept-encoding: gzip, deflate                                accept-language: en-us,en;q=0.8                                content-length: 317                                content-type: application/json;charset=utf-8                                cookie: [2043 bytes stripped]                                origin: https://qa2.web.com                                referer: https://qa2.web.com/payment/submit                                user-agent: mozilla/5.0 (macintosh; intel mac os x 10_10_4) applewebkit/537.36 (khtml, gecko) chrome/44.0.2403.89 safari/537.36 t=191706 [st=    1]     -http_transaction_send_request t=191706 [st=    1]     +http_transaction_read_headers  [dt=60079] t=191706 [st=    1]        http2_stream_update_send_window                            --> delta = -317                            --> stream_id = 313                            --> window_size = 65219 t=251785 [st=60080]        http2_stream_error                            --> description = "spdy stream closed status: 6"                            --> status = -337                            --> stream_id = 313 t=251785 [st=60080]     -http_transaction_read_headers                          --> net_error = -337 (err_spdy_protocol_error) t=251785 [st=60080]   -url_request_start_job                        --> net_error = -337 (err_spdy_protocol_error) t=251786 [st=60081]    url_request_delegate  [dt=0] t=251786 [st=60081] -request_alive                      --> net_error = -337 (err_spdy_protocol_error) 

here's quick workaround err_spdy_protocol_error:

  • open new tab in chrome browser
  • as url enter: chrome://net-internals/#events&q=type:spdy_session%20is:active
  • click on arrow in right corner
  • from drop-down menu click on flush sockets
  • try affected url again

enter image description here

in case, maybe necessary diagnose application behavior in-depth , why behavior triggers issue.

regards


Comments

Popular posts from this blog

javascript - Karma not able to start PhantomJS on Windows - Error: spawn UNKNOWN -

c# - Display ASPX Popup control in RowDeleteing Event (ASPX Gridview) -

Nuget pack csproj using nuspec -