* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #226 (closed editorial: incorporated)

Opened 5 years ago

Last modified 4 years ago

proxies not supporting certain methods

Reported by: julian.reschke@gmx.de Owned by: julian.reschke@gmx.de
Priority: normal Milestone: 13
Component: p2-semantics Severity: Active WG Document
Keywords: Cc:


Part 2, 9.1 says:

"A proxy MUST NOT modify the Allow header field even if it does not understand all the methods specified, since the user agent might have other means of communicating with the origin server."

That is *very* misleading as it implies that it's somehow ok for a proxy not to implement a method it doesn't know about. However, the transmission semantics for methods are generic (see Part 1, except for a few well-defined exceptions).

See related issue #53.

Change History

comment:1 Changed 5 years ago by mnot@pobox.com

I don't follow. It says "understand", not "implement." I.e., it doesn't imply that the proxy will reject the message, just that it doesn't recognise the method.

Perhaps it would be better to have a short introductory section about what it means for implementations to understand a method, status code, etc.? This might be useful for other situations as well.

comment:2 Changed 4 years ago by julian.reschke@gmx.de

The point I was trying to make is that proxies do not *have* to "understand" method to handle it properly; generic handling should be fine, right?

comment:3 Changed 4 years ago by mnot@pobox.com

  • Type changed from design to editorial

Of course. I think this is editorial; flip back to design if you disagree.

comment:4 Changed 4 years ago by julian.reschke@gmx.de

  • Owner set to julian.reschke@gmx.de
  • Milestone changed from unassigned to 13


"A proxy MUST NOT modify the Allow header field -- it doesn't need to understand all the methods specified in order to handle them according to the generic message handling rules."

comment:5 Changed 4 years ago by julian.reschke@gmx.de

From [1068]:

clarify proxy requirements wrt not-understood methods (see #226)

comment:6 Changed 4 years ago by julian.reschke@gmx.de

  • Status changed from new to closed
  • Resolution set to incorporated
Note: See TracTickets for help on using tickets.