Skip to content
This repository has been archived by the owner on Apr 8, 2019. It is now read-only.

GTNPORTAL-3361 - Added Cache-Control configuration option #759

Closed

Conversation

jpkrohling
Copy link
Contributor

Each portal now can set its own Cache-Control policy, the default being the value which is currently being used, for backwards compatibility.

Each portal now can set its own Cache-Control policy, the default being the value which is currently being used, for backwards compatibility.
@jpkrohling
Copy link
Contributor Author

As we talked on IRC, this change might open a way for an attack (HTTP Response Splitting). I'll be adding a new commit on top of this PR, that would prevent this.

@ppalaga
Copy link
Contributor

ppalaga commented Jan 15, 2014

Waiting for a fix of a potential HTTP header injection vulnerability.

@ppalaga
Copy link
Contributor

ppalaga commented Jan 15, 2014

Merged to master and 3.6.x.

@ppalaga ppalaga closed this Jan 15, 2014
@ppalaga
Copy link
Contributor

ppalaga commented Jan 15, 2014

Correction: Merged to master only.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants