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

Ticket #299 (closed design: wontfix)

Opened 5 years ago

Last modified 4 years ago

expand definition of 413 for header field size limits?

Reported by: julian.reschke@gmx.de Owned by:
Priority: normal Milestone: 18
Component: p2-semantics Severity: Active WG Document
Keywords: Cc:
Origin: http:///www.w3.org/mid/4E0DD74F.7090500@gmx.de


We should make a conscious decision about whether 413 can be used when a single header field is too big, or when the header section in total is too big.

Change History

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

...or define additional codes, as proposed by Roy in <http://lists.w3.org/Archives/Public/ietf-http-wg/2011JulSep/0010.html>.

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

  • Priority changed from normal to later

Marking as 'later' because draft-nottingham-http-new-status may address this.

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

  • Owner draft-ietf-httpbis-p2-semantics@tools.ietf.org deleted

comment:4 Changed 4 years ago by stpeter@stpeter.im

Note: I have accepted draft-nottingham-http-new-status as an AD-sponsored document and will be moving it forward soon.

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

  • Priority changed from later to normal
  • Status changed from new to closed
  • Resolution set to wontfix
  • Milestone changed from unassigned to 18
Note: See TracTickets for help on using tickets.