Shorter `TIMESTAMP` expiration period for production env
Issue #31
resolved
Currently it expires in 60 minutes for all envoronents. Ideally, each timestamped header should only be used once and expire every second. Allowing for system time difference, The expiration time should be around 5-10 minutes.
Comments (4)
-
-
reporter - changed status to resolved
fix: having a short timestamp expiration in prod while longer in dev/staging (fix
#31)→ <<cset bfed570f531d>>
-
reporter Merged in jimmychu0807/portal (pull request #63)
fix: having a short timestamp expiration in prod while longer in dev/staging (fix
#31)→ <<cset 6f7eca132ba1>>
-
- removed milestone
Removing milestone: Feb 16 (automated comment)
- Log in to comment