Merge lp:~mkanat/loggerhead/raw-prefix into lp:loggerhead
Proposed by
Max Kanat-Alexander
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Max Kanat-Alexander | ||||
Approved revision: | 442 | ||||
Merged at revision: | 440 | ||||
Proposed branch: | lp:~mkanat/loggerhead/raw-prefix | ||||
Merge into: | lp:loggerhead | ||||
Prerequisite: | lp:~mkanat/loggerhead/raw-controller | ||||
Diff against target: |
152 lines (+70/-2) 3 files modified
docs/serve-branches.rst (+18/-1) loggerhead/apps/transport.py (+46/-1) loggerhead/config.py (+6/-0) |
||||
To merge this branch: | bzr merge lp:~mkanat/loggerhead/raw-prefix | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Pool | Approve | ||
Review via email: mp+44682@code.launchpad.net |
Commit message
Add a --raw-prefix option for XSS protection on raw content.
Description of the change
This adds XSS protection to the raw-controller branch, by adding an option to serve raw content from a separate branch. I wanted this to be a separate landing so that it could get its own specific review. The docs I added for --raw-prefix should explain everything (and if they don't, then the docs should be updated).
To post a comment you must log in.
That looks good, and it's a nice clean fix.
iirc, there are now 3 options
0- don't serve arbitrary content except as attachments
1- serve it within the standard domain (trust it not to be malicious)
2- serve it from a different domain (with --raw-prefix)
With this and it's dependency merged, what's the default, 0 or 1? I hope it's 0 and you need to opt in to 1.