typofixes - https://github.com/vlajos/misspell_fixer
This commit is contained in:
@@ -144,7 +144,7 @@ void NgxBaseFetch::HandleHeadersComplete() {
|
|||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
// For the IPRO lookup, supress notification of the nginx side here.
|
// For the IPRO lookup, suppress notification of the nginx side here.
|
||||||
// If we send both this event and the one from done, nasty stuff will happen
|
// If we send both this event and the one from done, nasty stuff will happen
|
||||||
// if we loose the race with with the nginx side destructing this base fetch
|
// if we loose the race with with the nginx side destructing this base fetch
|
||||||
// instance (and thereby clearing the byte and its pending extraneous event.
|
// instance (and thereby clearing the byte and its pending extraneous event.
|
||||||
|
|||||||
+1
-1
@@ -447,7 +447,7 @@ const char* NgxFetch::str_url() {
|
|||||||
return str_url_.c_str();
|
return str_url_.c_str();
|
||||||
}
|
}
|
||||||
|
|
||||||
// This function should be called only once. The only argument is sucess or
|
// This function should be called only once. The only argument is success or
|
||||||
// not.
|
// not.
|
||||||
void NgxFetch::CallbackDone(bool success) {
|
void NgxFetch::CallbackDone(bool success) {
|
||||||
ngx_log_error(NGX_LOG_DEBUG, log_, 0, "NgxFetch %p: CallbackDone: %s\n",
|
ngx_log_error(NGX_LOG_DEBUG, log_, 0, "NgxFetch %p: CallbackDone: %s\n",
|
||||||
|
|||||||
@@ -59,7 +59,7 @@ class NgxUrlAsyncFetcher : public UrlAsyncFetcher {
|
|||||||
~NgxUrlAsyncFetcher();
|
~NgxUrlAsyncFetcher();
|
||||||
|
|
||||||
// It should be called in the module init_process callback function. Do some
|
// It should be called in the module init_process callback function. Do some
|
||||||
// intializations which can't be done in the master process
|
// initializations which can't be done in the master process
|
||||||
bool Init();
|
bool Init();
|
||||||
|
|
||||||
// shutdown all the fetches.
|
// shutdown all the fetches.
|
||||||
|
|||||||
Reference in New Issue
Block a user