The extension setting only affects the default presentation. Meta header
parsing is always enabled.
To use the X-ExtEditorR meta header as a literal custom header, escape
it by prepending an 'X-ExtEditorR-'.
That is, to send an 'X-ExtEditorR: foo' custom header, one can use
either 'X-ExtEditorR: X-ExtEditorR: foo' or 'X-ExtEditorR-X-ExtEditorR:
foo'; to send an 'X-ExtEditorR-Hello: foo', one can use either
'X-ExtEditorR: X-ExtEditorR-Hello: foo' or
'X-ExtEditorR-X-ExtEditorR-Hello: foo'.
Checklist
[x] I have rebased my branch so that it has no conflicts
Description
aa7f235feat: Support X-ExtEditorR meta headerThe extension setting only affects the default presentation. Meta header parsing is always enabled.
To use the X-ExtEditorR meta header as a literal custom header, escape it by prepending an 'X-ExtEditorR-'.
That is, to send an 'X-ExtEditorR: foo' custom header, one can use either 'X-ExtEditorR: X-ExtEditorR: foo' or 'X-ExtEditorR-X-ExtEditorR: foo'; to send an 'X-ExtEditorR-Hello: foo', one can use either 'X-ExtEditorR: X-ExtEditorR-Hello: foo' or 'X-ExtEditorR-X-ExtEditorR-Hello: foo'.
Checklist
Is this a breaking change?
No.
Previously
X-ExtEditorR*could be custom headers directly, but custom header has not been released.Test results
Closes #108