Opened 14 years ago

Closed 13 years ago

#157 closed editorial (fixed)

IP addresses in URLs

Reported by: mnot@… Owned by: fielding@…
Priority: normal Milestone: unassigned
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:

Description

Section 2.1.1 of part 1 is a bit too waffly about IP addresses, and what it wants to say is already covered in the meaning of SHOULD anyway. So:

OLD The use of IP addresses in URLs SHOULD be avoided whenever possible (see [RFC1900]).

NEW IP addresses SHOULD NOT be used in URLs (see [RFC1900]).

Technically, these say the same thing, so it's not a substantive change. But the second is in the active voice, and doesn't use the waffly "whenever possible" phrase.

Change History (3)

comment:1 Changed 13 years ago by fielding@…

  • Owner set to fielding@…
  • Priority set to normal
  • Status changed from new to assigned

The political statement intended by the original requirement was that people should not set up public Web servers and point to them using only an IP address because DNS (indirect names) is better. However, the way it was phrased is completely wrong. I am removing it from this specification because it should not be construed as a protocol constraint, but rather as Internet services documentation that is already provided elsewhere.

All significant consumer-oriented networking devices are configured using an http URI with a local IP address, as are most "managed" Internet devices.

comment:2 Changed 13 years ago by julian.reschke@…

From [627]:

Note change for issue 157 (related to #157)

comment:3 Changed 13 years ago by julian.reschke@…

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

statement was removed

Note: See TracTickets for help on using tickets.