The Network time is not the Date header

Time is how long the browser waited

In the Network panel, the Time column is the duration for that row. 84 ms means the browser measured about 84 milliseconds for that exchange. It is not a calendar time, and it will differ on the next reload.

Reload http://127.0.0.1:3000/invoices/1042 with the panel open and read the JSON row’s Time. Write the number with its unit. The unit is what keeps it from being filed as a clock.

Date is a header, or it is absent

Open the response headers for that same row. If Date is there, quote it as the Date header. That string is a clock the response carried. It is not the Time column, even when both are about the same fetch.

If Date is not in the header list, write that the Date header is not on this response. Do not convert 84 ms into a timestamp, and do not paste the time from your laptop clock into the header slot.

The note names the readout

File the path, the Time value, and the Date header or its absence. If you also have a Burp history time for the same call, label that as the proxy time. Three clocks stay three lines.

Worked case: 84 ms filed as the server clock

On the invoice page, the JSON row shows Time 84 ms, or whatever your panel shows. The draft writes “server time 84 ms” and does not open the headers. Replace 84 with your number if it differs, and keep the unit.

Open the headers. Either quote Date exactly, or write that it is absent. The duration stays the Time column. The draft’s server-time sentence is removed unless a Date header is actually there, and even then the Date is quoted as Date.

page: http://127.0.0.1:3000/invoices/1042
row: GET /api/invoices/1042
time column: 84 ms, or the value you see
date header: quote it, or not on this response
write: duration and header separately
not: server time 84 ms