Opened 9 years ago

Closed 8 years ago

#288 closed design (fixed)

Considering messages in isolation

Reported by: mnot@… Owned by: julian.reschke@…
Priority: normal Milestone: 15
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:

Description

We need to explicitly require each and every HTTP message on the wire to be considered in isolation.

E.g., it's reported that some load balancers can be configured to route the message based upon only the first message's Host header per connection.

Likewise, some broken authentication schemes rely on keeping state between messages in a connection.

Change History (9)

comment:1 Changed 9 years ago by mnot@…

Probably appropriate in the section on persistent connections (or at least link from there).

comment:2 Changed 8 years ago by mnot@…

Add to new message orientation section (see #283) or just to 2.2 Client/Server? messaging:

Recipients MUST consider every message in a connection in isolation; because HTTP is a stateless protocol, it cannot be assumed that two requests on the same connection are from the same client or share any other common attributes.

comment:3 Changed 8 years ago by mnot@…

  • Milestone changed from unassigned to 15

comment:4 Changed 8 years ago by julian.reschke@…

  • Owner set to julian.reschke@…
  • Status changed from new to assigned

comment:5 Changed 8 years ago by julian.reschke@…

From [1317]:

explain that messages need to be considered in isolation (see #288)

comment:6 Changed 8 years ago by julian.reschke@…

  • Resolution set to incorporated
  • Status changed from assigned to closed

comment:7 Changed 8 years ago by julian.reschke@…

From [1324]:

mention NTLM as something that violates the stalessness requirement (see #288)

comment:8 Changed 8 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:9 Changed 8 years ago by mnot@…

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