$r->header(':__X_Y__', 1);
It also mentions why $TRANSLATE_UNDERSCORE has been undocumented,
so there's probably little point in requesting a "documentation enhancement"
such as I suggested.
There's no mention of using the colon prefix in the documentation for the header() methods
of either HTTP::Request or HTTP::Headers.
The latter could probably at least supply a link to the short section, right at the end of its doco,
which explains it:
"NON-CANONICALIZED FIELD NAMES".
"... (convenience features that change data should be explicitely turned on, rather than turned off) ..."
In general, I'd agree with that statement.
In this specific case, I'm not so sure:
that particular feature is, I suspect, exactly what the vast majority of users want;
I've certainly never needed it to work differently.
Having said that, I do think such features need to be well documented:
in this instance, it probably just needs a short sentence with a L<...> added to the POD.
Update (fix):
Oops! I left out a word which completely changed the intended meaning:
s{I'm so sure}{I'm not so sure}.
|