nmemmert 2e406af471 Add ALLOW_INSECURE_COOKIES env flag for HTTP access in production ...

Browsers drop Secure cookies on plain-http origins, so logging into the
admin over a LAN/VPN IP (e.g. during server migration, before TLS is in
front) silently failed every authenticated request. Setting
ALLOW_INSECURE_COOKIES=true omits the Secure flag; default behavior in
production is unchanged.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-07 12:49:37 -04:00

..

routes

Add full /data backup export/import for server migration

2026-07-07 12:08:23 -04:00

auth.js

Add ALLOW_INSECURE_COOKIES env flag for HTTP access in production

2026-07-07 12:49:37 -04:00

config.js

Add full /data backup export/import for server migration

2026-07-07 12:08:23 -04:00

data.js

Fix inbound-email data loss, MIME truncation, and header injection

2026-07-02 08:21:50 -04:00

email.js

All green. You're good to build and deploy. Here's a summary of everything done since your last commit:

2026-06-04 09:17:34 -04:00

helpers.js

Add ALLOW_INSECURE_COOKIES env flag for HTTP access in production

2026-07-07 12:49:37 -04:00

paths.js

Add full /data backup export/import for server migration

2026-07-07 12:08:23 -04:00

state.js

Add comprehensive visitor engagement tracking and scroll-to-top on navigation

2026-06-17 14:06:21 -04:00

study-helpers.js

Add ALLOW_INSECURE_COOKIES env flag for HTTP access in production

2026-07-07 12:49:37 -04:00