mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #57070
[Bug 1855561] A change has been merged
Reviewed: https://reviews.mahara.org/10655
Committed: https://git.mahara.org/mahara/mahara/commit/db53b4de12a6cbf5fcfc60c9973a64d976b5a4e2
Submitter: Cecilia Vela Gurovic (ceciliavg@xxxxxxxxxxxxxxx)
Branch: master
commit db53b4de12a6cbf5fcfc60c9973a64d976b5a4e2
Author: Robert Lyon <robertl@xxxxxxxxxxxxxxx>
Date: Sun Dec 8 11:26:03 2019 +1300
Bug 1855561: Only set the Strict-Transport-Security header if needed
If the server has already set this header we shouldn't set it again
behatnotneeded
Change-Id: I75557594dcb6e84ae9fc0c6dc0988fcdb1312222
Signed-off-by: Robert Lyon <robertl@xxxxxxxxxxxxxxx>
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1855561
Title:
Only set the Strict-Transport-Security header once
Status in Mahara:
Fix Committed
Bug description:
If the underlying server is already setting this header we should not
get Mahara to set it in case they are setting it to different values
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1855561/+subscriptions
References