feat: skeleton key bullet proof. 10 min cache on city search response
* feat: skeleton key bullet proof. 10 min cache on city search response
* Refactor server.ts
Approved-by: Michael Zetterberg
First steps towards the SAS partnership
* otp flow now pretends to do the linking
* Update LinkAccountForm header
* Update redirect times
* Clean up comments
* Set maxAge on sas cookies
* make all SAS routes protected
* Merge remote-tracking branch 'refs/remotes/origin/feature/sas-login' into feature/sas-login
* Require auth for sas link flow
* Fix resend otp
* Add error support to OneTimePasswordForm
* Add Sentry to SAS error boundary
* Move SAS_REQUEST_OTP_STATE_STORAGE_COOKIE_NAME
* Add missing translations
* Merge branch 'master' of bitbucket.org:scandic-swap/web into feature/sas-login
* Merge branch 'feature/sas-login' of bitbucket.org:scandic-swap/web into feature/sas-login
* Add TooManyCodesError component
* Refactor GenericError to support new errors
* Add FailedAttemptsError
* remove removed component <VWOScript/>
* Merge branch 'feature/sas-login' of bitbucket.org:scandic-swap/web into feature/sas-login
* remove local cookie-bot reference
* Fix sas campaign logo scaling
* feature toggle the SAS stuff
* Merge branch 'feature/sas-login' of bitbucket.org:scandic-swap/web into feature/sas-login
* fix: use env vars for SAS endpoints
Approved-by: Linus Flood
fix: reduce the need for multiple SEAMLESS_LOGIN/SEAMLESS_LOGOUT
* fix: reduce the need for multiple SEAMLESS_LOGIN/SEAMLESS_LOGOUT
* fix: reduce the need for multiple SEAMLESS_LOGIN/SEAMLESS_LOGOUT
* fix: defaulted values that are the same in each environment
Approved-by: Christian Andolf
Approved-by: Linus Flood
fix(SW-1160): include current header as sticky
* fix(SW-1160): include current header as sticky
* fix(sw-1160): only count with current header height if its shown
Approved-by: Erik Tiekstra
These are now defined in Netlify UI for dedicated environments (test, stage, production):
AUTH_URL
NEXTAUTH_URL
PUBLIC_URL
Code now falls back to incoming request host. Mainly used for
deployment previews which do not have Akamai in front, meaning
we do not need the above workaround as incoming request host
matches the actual public facing host. When Akamai is in front,
we lose the public facing host in Netlify's routing layer as they
internally use `x-forwarded-for` and we can't claim it for our usage.
