Open jeffkaufman opened 10 years ago
It seems likely that #774 and #776 are related.
@dinic are you still up for debugging native fetcher issues?
I suspect #774 is easier to debug, because it's effectively synchronous: the initial request has to wait until the response gets passed all the way through.
The problem might be as simple as too low a timeout somewhere in the native fetcher.
The problem might be as simple as too low a timeout somewhere in the native fetcher.
I just did a quick check to make sure we haven't screwed up the units with the timer, and we haven't. It's milliseconds all the way down:
ngx_rewrite_driver_factory.cc:
NgxUrlAsyncFetcher* fetcher = new NgxUrlAsyncFetcher(
...
config->blocking_fetch_timeout_ms(),
...)
ngx_url_async_fetcher.cc:
fetch_timeout_ = fetch_timeout;
ngx_fetch.cc:
ngx_add_timer(timeout_event_, fetcher_->fetch_timeout_);
event/ngx_event.h:
#define ngx_add_timer ngx_event_add_timer
event/ngx_event_timer.h:
ngx_event_add_timer(ngx_event_t *ev, ngx_msec_t timer)
Example output, also added to #774: www.jefftk.com/ngx_pagespeed_issue_776_test_output.txt
To reproduce faster:
Observe:
EDIT: The trace shown above (first no
@font-face
included, then@font-face
consistently included) is fine. The problem is that, at least on my system, we go back to no@font-face
after a while.