|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
The problem is that the plugin cannot suppress the header entirely; it can only set the header value to the empty string. Which seems to work in practice but might be illegal. So something ought to be done in core. This could be minimal, as in recognizing a system property to suppress its normal behavior that the plugin would set; but that is also a hack from a design perspective—generally we prefer to have behavior driven by extension points, with plugins adding options according to a documented SPI.