Mercurial > hg
view tests/test-narrow-debugrebuilddirstate.t @ 37828:3e3acf5d6a07 stable
hgweb: allow Content-Security-Policy header on 304 responses (issue5844)
A side-effect of 98baf8dea553 was that the Content-Security-Policy
header was set on all HTTP responses by default. This header wasn't
in our list of allowed headers for HTTP 304 responses. This would
trigger a ProgrammingError when a 304 response was issued via hgwebdir.
This commit adds Content-Security-Policy to the allow list of headers
for 304 responses so we no longer encounter the error.
Differential Revision: https://phab.mercurial-scm.org/D3436
author | Gregory Szorc <gregory.szorc@gmail.com> |
---|---|
date | Mon, 30 Apr 2018 17:28:59 -0700 |
parents | a2a6e724d61a |
children | 01c0f01b562b |
line wrap: on
line source
$ . "$TESTDIR/narrow-library.sh" $ hg init master $ cd master $ echo treemanifest >> .hg/requires $ echo 'contents of file' > file $ mkdir foo $ echo 'contents of foo/bar' > foo/bar $ hg ci -Am 'some change' adding file adding foo/bar $ cd .. $ hg clone --narrow ssh://user@dummy/master copy --include=foo requesting all changes adding changesets adding manifests adding file changes added 1 changesets with 1 changes to 1 files new changesets * (glob) updating to branch default 1 files updated, 0 files merged, 0 files removed, 0 files unresolved $ cd copy $ hg debugdirstate n * 20 unset foo/bar (glob) $ mv .hg/dirstate .hg/old_dirstate $ dd bs=40 count=1 if=.hg/old_dirstate of=.hg/dirstate 2>/dev/null $ hg debugdirstate $ hg debugrebuilddirstate $ hg debugdirstate n * * unset foo/bar (glob)