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

Ticket #157 (closed editorial: fixed)

Opened 5 years ago

Last modified 5 years ago

IP addresses in URLs

Reported by: mnot@pobox.com Owned by: fielding@gbiv.com
Priority: normal Milestone: unassigned
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/6c9fcc2a0903260948p76b108e8i74eafd15875dff27@mail.gmail.com

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

comment:1 Changed 5 years ago by fielding@gbiv.com

  • Owner set to fielding@gbiv.com
  • 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 5 years ago by julian.reschke@gmx.de

From [627]:

Note change for issue 157 (related to #157)

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

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

statement was removed

Note: See TracTickets for help on using tickets.