hkwtf / cnpaas-portal / issues / #31 - Shorter `TIMESTAMP` expiration period for production env — Bitbucket

Issue #31 resolved

LiAh Sheep created an issue 2015-02-09

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)

Jimmy Chu
- changed milestone to Feb 16
- assigned issue to
  
  Jimmy Chu
- 2015-02-09T10:09:51+00:00
LiAh Sheep reporter
- changed status to resolved
fix: having a short timestamp expiration in prod while longer in dev/staging (fix ~~#31~~)

→ <<cset bfed570f531d>>
- 2015-02-10T03:07:16+00:00
LiAh Sheep 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>>
- 2015-02-10T03:07:16+00:00
Jimmy Chu
- removed milestone
Removing milestone: Feb 16 (automated comment)
- 2015-04-09T03:25:37+00:00
Log in to comment

Assignee: Jimmy Chu

Type: bug

Priority: minor

Status: resolved

Component: –

Milestone: –

Votes: 0

Watchers: 2