Proxy needs to be immune to the change of the time on a local proxy machine

[gregschohn]

What is the bug?

Instant.now() is used for timestamps of TrafficObservations, which doesn't guarantee monotonicity.

How can one reproduce the bug?

I haven't confirmed this scenario, but it would be a good test too. Run the proxy. Open a connection to the proxy with keep-alive enabled.

1. Run a request through the proxy (to a backend server).
2. Reset the clock backward on the system by a couple seconds.
3. Send another request through.

The timestamps should be in chronological order, even if that means that the timestamp doesn't match the currently reported time of the host machine.

What is the expected behavior?

All observations within a connection will be in chronological order.

What is your host/environment?

N/A

Do you have any screenshots?

N/A

Do you have any additional context?

See Issue 536

[peternied]

@gregschohn Which component should arbitrate 'time', it seems like it should be the proxy?