From 7025d6656a127d18ac1ef4f29a912181308c6971 Mon Sep 17 00:00:00 2001 From: Valdir Stumm Junior Date: Tue, 18 Oct 2016 11:51:13 -0200 Subject: [PATCH] document download_latency meta key --- docs/topics/request-response.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/topics/request-response.rst b/docs/topics/request-response.rst index 75b98d3b3..7e700c7cb 100644 --- a/docs/topics/request-response.rst +++ b/docs/topics/request-response.rst @@ -299,6 +299,7 @@ Those are: * :reqmeta:`dont_obey_robotstxt` * :reqmeta:`download_timeout` * :reqmeta:`download_maxsize` +* :reqmeta:`download_latency` * :reqmeta:`proxy` .. reqmeta:: bindaddress @@ -316,6 +317,15 @@ download_timeout The amount of time (in secs) that the downloader will wait before timing out. See also: :setting:`DOWNLOAD_TIMEOUT`. +.. reqmeta:: download_latency + +download_latency +---------------- + +The amount of time spent to fetch the response, since the request has been +started, i.e. HTTP message sent over the network. This meta key only becomes +available when the response has been downloaded. While most other meta keys are +used to control Scrapy behavior, this one is supposed to be read-only. .. _topics-request-response-ref-request-subclasses: