why server processing is 0 with local request

Open
#44 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

Reproduce the local request using the curl 7.61.1 output and the HTTPSTAT_SHOW_IP, HTTPSTAT_SHOW_SPEED, HTTPSTAT_SAVE_BODY, and HTTPSTAT_DEBUG settings shown. Trace how httpstat derives the starttransfer and total timings, then determine why server processing is displayed as 0ms despite a 1405ms content transfer; no source file or test is named in the issue.

Written by the indexing model from the issue text.

Description

curl 7.61.1 (x86_64-redhat-linux-gnu) libcurl/7.61.1 OpenSSL/1.1.1c zlib/1.2.11 brotli/1.0.6 libidn2/2.2.0 libpsl/0.20.2 (+libidn2/2.0.5) libssh/0.9.0/openssl/zlib nghttp2/1.33.0

export  HTTPSTAT_SHOW_IP=true
export  HTTPSTAT_SHOW_SPEED=true
export  HTTPSTAT_SAVE_BODY=false
export  HTTPSTAT_DEBUG=false

Connected to ::1:8094 from ::1:57934

HTTP/1.1 100 Continue

HTTP/1.1 200 OK
Content-Type: application/json
Grpc-Metadata-Content-Type: application/grpc
Date: Tue, 31 Aug 2021 12:33:30 GMT
Content-Length: 258

  DNS Lookup   TCP Connection   Server Processing   Content Transfer
[     0ms    |       0ms      |        0ms        |      1405ms      ]
             |                |                   |                  |
    namelookup:0ms            |                   |                  |
                        connect:0ms               |                  |
                                      starttransfer:0ms              |
                                                                 total:1405ms

speed_download: 0.2 KiB/s, speed_upload: 36791.2 KiB/s

Dominant language
Python
Stars
6.2k
Forks
384
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from reorx/httpstat

All issues in reorx/httpstat

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.