Opened 4 years ago

Last modified 2 months ago

#327 new defect

Disambiguate URL-PATHNAME from logical pathnames

Reported by: mevenson Owned by: ehuelsmann
Priority: blocker Milestone: 1.6.0
Component: interpreter Version: 1.3.0-dev
Keywords: url-pathname logical-pathname Cc:
Parent Tickets:

Description

Karsten notes problems with trying to use logical pathnames for a host that also could be a URI schema:

I completely understand that it is desirable to have
(load "http://beta.quicklisp.org/quicklisp.lisp") working, but can't you
check for "http://" or "https://" before converting a pathname to an
url-pathname?

A reasonable request. URL-PATHNAMEs are actually [uris][1], which we can distinguish by having a "/" immediately after the ":" so I think we are in good shape to implement this in a sane manner that covers all possible cases, not those just with "http" and "https" schemas.

[1]: https://en.wikipedia.org/wiki/URI_scheme#Generic_syntax

Subtickets (add)

Change History (7)

comment:1 Changed 4 years ago by mevenson

1) its "scheme" not "schema"

2) a URN is a valid URI, it is has a hierarchy separated on #\: such as

    urn:this:is:the:path.lisp

so the strategy of looking immediately for a #\/ after the possible naming of a logical pathname is a little more complicated.

comment:2 Changed 4 years ago by mevenson

  • Priority changed from major to blocker

comment:3 Changed 3 years ago by mevenson

  • Milestone changed from 1.3.0 to 2.0

Ticket retargeted after milestone closed

comment:4 Changed 3 years ago by mevenson

  • Milestone changed from 2.0 to 2.0.0

Milestone renamed

comment:5 Changed 3 years ago by mevenson

  • Milestone changed from 2.0.0 to 1.4.0

comment:6 Changed 11 months ago by mevenson

  • Milestone changed from 1.4.0 to 1.5.0

Ticket retargeted after milestone closed

comment:7 Changed 2 months ago by mevenson

  • Milestone changed from 1.5.0 to 1.6.0

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.