[TYPO3-core] RFC: #15626: Feature: Add stdWrap to config.additionalHeaders

[Rik Willems]

Hi all,

Just a little bump for this one. I'm willing to implement this but need 
to know if it would have any chance.

So, can config.* OR config.additionalHeaders have stdWrap or not? OR 
would page.additionalHeaders be a nice alternative?

Cheers Rik


Op 7-9-2010 0:12, Rik Willems schreef:
>> The main issue with using stdWrap on these properties, is that there
>> isn't necessarily access to a valid cObj when certain properties are
>> being read, so usually you don't even have access to TypoScript. Some of
>> the setting even affect how "stdWrap" behaves (e.g. "locale_all").
>>
>> So it is right that the config.* top level array (and its page.config.*
>> brothers) are a place where "miscelaneous" settings are made, but we can
>> still have stdWrap in certain situations, and this is one of it. In this
>> case, additionalHeaders give out HTTP-headers, which you cannot do with
>> "page.headerData" level (you can only "emulate" them).
>
> So you think your first paragraph and second paragraph can be united? In
> the last case I will propose a new patch according to Joey's suggestions.
>
> Both options sound valid to me. But if the page.config remains a flat
> config array there should be another way to make the additional headers,
> right? Perhaps page.additionalHeaders could be an option?
>
> Cheers, Rik