# Client replay doesn't update request timestamps

**URL:** <https://discourse.mitmproxy.org/t/client-replay-doesnt-update-request-timestamps/1217>\
**Category:** help\
**Created:** [September 7, 2018, 8:26am UTC](https://discourse.mitmproxy.org/t/client-replay-doesnt-update-request-timestamps/1217 "2018-09-07T08:26:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kjk](https://avatars.discourse-cdn.com/v4/letter/k/db5fbb/32.png) [@kjk](https://discourse.mitmproxy.org/u/kjk)\
**Post date:** [September 7, 2018, 8:26am UTC](https://discourse.mitmproxy.org/t/client-replay-doesnt-update-request-timestamps/1217/1 "2018-09-07T08:26:19Z")

</div>

##### Steps to reproduce the problem:

1. Save flows to a file, `saved.mitm`
2. Wait a few minutes
3. Use a command like `mitmdump -n -C saved.mitm -s myscript.py -w replayed.mtim` to replay the saved flows.
4. The observe the flows with `mitmproxy -n -r replayed.mitm` and see that the request-response time of the flows are inaccurate because it seems to be calculated using the start time of the requests in `saved.mitm`.

##### Any other comments? What have you tried so far?

If such behavior is intentional, what’s the recommended way to set the request timestamps so that they reflect the time when the requests are actually replayed rather than the previously saved timestamps?

##### System information

Mitmproxy: 4.0.4  
Python: 3.7.0  
OpenSSL: OpenSSL 1.0.2p 14 Aug 2018  
Platform: Darwin-17.5.0-x86\_64-i386-64bit

---

<div class="post-metadata">

**Author:** ![rjt-gupta](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.mitmproxy.org/rjt-gupta/32/411_2.png) [@rjt-gupta](https://discourse.mitmproxy.org/u/rjt-gupta)\
**Post date:** [March 11, 2019, 8:27pm UTC](https://discourse.mitmproxy.org/t/client-replay-doesnt-update-request-timestamps/1217/2 "2019-03-11T20:27:15Z")

</div>

I believe this is fixed now. refs - [here](https://github.com/mitmproxy/mitmproxy/pull/3401)