[jboss-jira] [JBoss JIRA] (WFWIP-284) Clarify what is invalid header name
Marek Kopecky (Jira)
issues at jboss.org
Thu Dec 12 01:00:01 EST 2019
[ https://issues.redhat.com/browse/WFWIP-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13824200#comment-13824200 ]
Marek Kopecky edited comment on WFWIP-284 at 12/12/19 12:59 AM:
----------------------------------------------------------------
[~dlofthouse]: Looking to RFC2616 that you linked:
{noformat}
Obsoleted by: 7230, 7231, 7232, 7233, 7234, 7235
Updated by: 2817, 5785, 6266, 6585
{noformat}
Looking to RFC5322 that Tomas linked: it seems that this RFC is not obsoleted.
Can you link some non-obsoleted RFC?
was (Author: mkopecky):
[~dlofthouse]: Looking to RFC2616 that you linked:
{noformat}
Obsoleted by: 7230, 7231, 7232, 7233, 7234, 7235
Updated by: 2817, 5785, 6266, 6585
{noformat}
Looking to rfc5322 that Tomas linked: it seems that this RFC is not obsoleted. Can you link some non-obsoleted RFC?
> Clarify what is invalid header name
> -----------------------------------
>
> Key: WFWIP-284
> URL: https://issues.redhat.com/browse/WFWIP-284
> Project: WildFly WIP
> Issue Type: Task
> Reporter: Tomas Terem
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: management
>
> Header names should follow rules described here:
> https://tools.ietf.org/html/rfc5322#section-2.2
> However, rules for custom headers seems to be more restrictive - for example @ or = are not allowed.
> I see that these characters are mentioned in https://tools.ietf.org/html/rfc2616#page-16, but it only says that they should be in quotes. However I am not able to configure header containing them in quotes either.
> Is this on purpose?
> If yes, this needs to be mentioned in analysis&documentation. If not, we need to create critical JBEAP jira for 7.4
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the jboss-jira
mailing list