OhHeyAlan 4fad9d672f Correcting X-XSS-Protection Header (#136) ...

* Correcting X-XSS-Protection Header

X-XSS-Protection sets the configuration for the cross-site scripting filters built into most browsers. The best configuration is "X-XSS-Protection: 1; mode=block".

Was "0"
Now "1; mode=block"

* Update issue templates

2019-05-08 10:11:05 +10:00

..

internal

This commit resolves #98 so custom location can forward to custom path. (#99)

2019-03-11 13:52:09 +10:00

lib

Default Site customisation and new Settings space (#91)

2019-03-04 21:19:36 +10:00

migrations

Feature/custom locations (#74)

2019-03-05 08:21:02 +10:00

models

Feature/custom locations (#74)

2019-03-05 08:21:02 +10:00

routes

Fixed directory traversal vulnerability. (#114)

2019-04-03 08:37:40 +10:00

schema

This commit resolves #98 so custom location can forward to custom path. (#99)

2019-03-11 13:52:09 +10:00

templates

This commit resolves #98 so custom location can forward to custom path. (#99)

2019-03-11 13:52:09 +10:00

views

Fix redirect loop introduced in 2.0.4

2018-11-08 12:50:10 +10:00

app.js

Correcting X-XSS-Protection Header (#136)

2019-05-08 10:11:05 +10:00

db.js

Split out docs, better error handling when database config doesn't exist

2018-08-01 10:04:34 +10:00

importer.js

Host or IP specified for Proxy Host Forward

2018-10-19 15:38:14 +10:00

index.js

Fixes #88 - Allow specifying X-FRAME-OPTIONS with an environment variable (#89)

2019-03-04 10:16:46 +10:00

logger.js

Fetch ip ranges for CDN servers, Cloudfront and Cloudfare

2019-01-03 17:04:53 +10:00

migrate.js

Backend

2018-06-20 08:47:26 +10:00

setup.js

Fixes #11 - After creating keys the app needs to completely restart due to aggressive module caching

2018-09-12 11:14:06 +10:00