diff options
| author | Vasudev Kamath <kamathvasudev@gmail.com> | 2014-03-01 12:33:03 +0530 |
|---|---|---|
| committer | Vasudev Kamath <kamathvasudev@gmail.com> | 2014-03-01 12:33:03 +0530 |
| commit | 63aeabadc100c8a9ba53d94b6ba9ce48089c35af (patch) | |
| tree | 674003bc333837d9bf1798de0ab7828c27fd5392 | |
| parent | 2ba251d46faa2c1277452c8d4df89dad2a8a7945 (diff) | |
fix image paths
| -rw-r--r-- | content/development/comressed_response.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/content/development/comressed_response.rst b/content/development/comressed_response.rst index 2bbe259..243758f 100644 --- a/content/development/comressed_response.rst +++ b/content/development/comressed_response.rst @@ -53,14 +53,14 @@ iceweasel to observe the network traffic. And below is what I observed in firebug network console!. -.. image:: images/no-response-css.png +.. image:: {filename}/images/no-response-css.png :alt: No response headers :align: center So you can see no response header in the above image but there is a response and below how is response content visible on firebug. -.. image:: images/response-content.png +.. image:: {filename}/images/response-content.png :alt: gzipped response :align: center @@ -117,7 +117,7 @@ behavior depends on internal implementation of **mod_uwsgi** and request response in **Firebug** network console and below is what I observed. -.. image:: images/response-content-uwsgi-proxy.png +.. image:: {filename}/images/response-content-uwsgi-proxy.png :alt: Response with mod_proxy_uwsgi :align: center |