Ticket #5031 (closed Bug: wontfix)
plone sends no Vary: Accept-Language
| Reported by: | bastian@… | Owned by: | plonista |
|---|---|---|---|
| Priority: | major | Milestone: | 2.5.2 |
| Component: | Infrastructure | Keywords: | |
| Cc: |
Description
plone sends no Vary: Accept-Language even if it decides to change the language of the ui on this header.
Change History
comment:1 Changed 6 years ago by hannosch
- Component changed from Unknown to Infrastructure
- Milestone set to 2.1.x
comment:3 Changed 6 years ago by hannosch
- Owner changed from somebody to hannosch
- Component changed from Infrastructure to Internationalization
comment:4 Changed 6 years ago by limi
- Milestone changed from 2.5.x to 2.5.1
Hanno, can you look at this as part of the i18n fixes for 2.5.1?
comment:5 Changed 6 years ago by hannosch
- Owner changed from hannosch to plonista
- Component changed from Internationalization to Infrastructure
Ok, I looked a bit into this. If I understand the Vary header correctly it is only used by proxy caches, to determine if a page can be served from the cache or not.
While Plone itself indeed does not send a Vary header, it's most prominent caching product CacheFu handles this case and allows customization of this header as well. I'm inclined to close this ticket as it is now, as you should install CacheFu anyways if you care about proxy caching of any kind.
If somebody thinks that we should emit this header in Plone core nonetheless, it has to happen in a way that plays nicely with CacheFu, i.e. allows CacheFu to overwrite this setting again. Btw. CacheFu emits both a Vary: Accept-Encoding and Accept-Language per default setting.
As I don't have any clue about how to change the response in a recustomizable way I won't have much luck with this issue, handing over to our caching master ;)
comment:6 Changed 5 years ago by hannosch
- Milestone changed from 2.5.1 to 2.5.x
This is too much of a change for 2.5.1 rescheduling.
