awww man, that is so crappy - I read that code wrong; I thought we fixed
that :'(
default_allowed_headers = '''
content-disposition,
content-encoding,
x-delete-at,
x-object-manifest,
x-static-large-object,
'''
extra_allowed_headers = [
header.strip().lower() for header in conf.get(
'allowed_headers', default_allowed_headers).split(',')
if header.strip()
]
self.allowed_headers = set()
for header in extra_allowed_headers:
if header not in DATAFILE_SYSTEM_META:
self.allowed_headers.add(header)
That's such a junky option the way it's written - i think i was in there
last, I should have fixed it then. Who wants to turn off the
x-object-manifest header!? We should open a bug...
Maybe this will help:
https://bugs.launchpad.net/swift/+bug/1354312
On Thu, Aug 7, 2014 at 11:19 PM, Robert van Leeuwen <
robert.vanleeu...@spilgames.com> wrote:
> >No, i was thinking of "allowed_headers", when I add:
> >
>
> > [DEFAULT]
>
> > allowed_headers = expires
>
> Note that when you set allowed headers to something specific it will not
> allow the defaults anymore!
> You might not notice immediately but e.g. large file support will break.
>
> Example: Cache-Control is the one that we added in our setup:
> allowed_headers = Content-Disposition, Content-Encoding, X-Delete-At,
> X-Object-Manifest, X-Static-Large-Object, Cache-Control
>
> Cheers,
> Robert van Leeuwen
>
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
