Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #35005
| Path | csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail |
|---|---|
| From | Martin Gregorie <martin@address-in-sig.invalid> |
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: Disappearing API docs |
| Date | Wed, 20 Jul 2016 11:45:18 -0000 (UTC) |
| Organization | A noiseless patient Spider |
| Lines | 84 |
| Message-ID | <nmno8d$dhv$1@dont-email.me> (permalink) |
| References | <clbsob9mf191c87jb62cvf6i2j20u8s354@4ax.com> <1017aa77-c4fe-43f4-8195-4627cbc06e99@googlegroups.com> <eb952c34-012a-4ef8-8d1f-8d0b18c58294@googlegroups.com> <4dvsobh2bbgkq66caohursk91t8bn9iuij@4ax.com> <ffaca21f-9ab8-44f4-aa0c-edb2b27cd20a@googlegroups.com> <nmmh9t$164r$1@gioia.aioe.org> |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=UTF-8 |
| Content-Transfer-Encoding | 8bit |
| Injection-Date | Wed, 20 Jul 2016 11:45:18 -0000 (UTC) |
| Injection-Info | mx02.eternal-september.org; posting-host="e5160e2be48f1ea550cf61512446f525"; logging-data="13887"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+cS86GZeReKYyEICC6fBBj/bT4pCuqMNA=" |
| User-Agent | Pan/0.140 (Chocolate Salty Balls; GIT 3663720 git://git.gnome.org/pan2) |
| Cancel-Lock | sha1:QjWs+97Iv9V4E5vREoHRN1iyPqA= |
| Xref | csiph.com comp.lang.java.programmer:35005 |
Show key headers only | View raw
On Tue, 19 Jul 2016 20:40:30 -0400, Arne Vajhøj wrote: > On 7/19/2016 3:49 PM, Eric Douglas wrote: >> On Tuesday, July 19, 2016 at 3:23:48 PM UTC-4, Roedy Green wrote: >>> Put it this way, I had all kinds of reference in my website with >>> Javase. My link checker warns me of broken links after failing 5 >>> days. It went off this morning. Perhaps Oracle have just stopped >>> accepting Javase as an alternate. >> >> It does seem odd. I put these in Chrome: >> http://docs.oracle.com/javase/8/docs/api/ is a valid web site. >> http://docs.oracle.com/Javase/8/docs/api/ is not a valid web site. >> https://www.google.com/ is a valid web site. >> https://www.gOOglE.coM/ redirects to https://www.google.com/ >> https://yAhOo.CoM redirects to https://www.yahoo.com/ >> >> FTP paths would be case sensitive if the server is unix based. I >> didn't think web sites were. > > Hostnames are not case sensitive. > > RFC 952 for host names say: > > "No distinction is made between upper and lower case." > > RFC 3986 for URI's say: > > "Although host is case-insensitive, producers and normalizers should use > lowercase for registered names" > > Paths may be case sensitive. > > https://www.w3.org/TR/WD-html40-970708/htmlweb.html > > say: > > "URLs in general are case-sensitive (with the exception of machine > names). There may be URLs, or parts of URLs, where case doesn't matter, > but identifying these may not be easy. Users should always consider that > URLs are case-sensitive." > > I think that in practice path is case sensitive when mapped to a case > sensitive file system and case in-sensitive when mapped to a case > in-sensitive file system. > > It is just practical. > > Assume you have a dir with: > > x.html X.html > > For case sensitive path then it is easy: > > http://blabla/x.html gets x.html http://blabla/X.html gets X.html > > For case in-sensitive path then I am not sure what these URL's should > return: > > http://blabla/x.html http://blabla/X.html > They both return the same file because there's only the one item in a case agnostic filing system. It should be selected regardless of the case used to do so. The following is based on the behaviour of Microware's OS/9, formerly quite a popular real-time OS, but I'm pretty sure that all case- insensitive OSes would work the same way. OS/9 allows you to use upper,lower or mixed case to name a new file or directory and gives it the name exactly as typed, but it does caseless comparisons when looking for an existing file or directory. The common convention was to use UPPER-CASE for naming directories and lower case for naming files and devices. Since directory listings are always lexicographically sorted, this means that directories will appear first, followed by files. However, commands that reference existing files and directories can be written entirely in lower case. HTH -- martin@ | Martin Gregorie gregorie. | Essex, UK org |
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Disappearing API docs Roedy Green <inquiry@mindprod.com> - 2016-07-19 06:46 -0700
Re: Disappearing API docs Eric Douglas <e.d.programmer@gmail.com> - 2016-07-19 06:54 -0700
Re: Disappearing API docs Lew <lewbloch@gmail.com> - 2016-07-19 10:36 -0700
Re: Disappearing API docs Roedy Green <inquiry@mindprod.com> - 2016-07-19 12:23 -0700
Re: Disappearing API docs Eric Douglas <e.d.programmer@gmail.com> - 2016-07-19 12:49 -0700
Re: Disappearing API docs Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-19 20:31 +0000
Re: Disappearing API docs Eric Douglas <e.d.programmer@gmail.com> - 2016-07-19 13:59 -0700
Re: Disappearing API docs Lew <lewbloch@gmail.com> - 2016-07-19 14:52 -0700
Re: Disappearing API docs Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-19 22:03 +0000
Re: Disappearing API docs Eric Douglas <e.d.programmer@gmail.com> - 2016-07-20 05:36 -0700
Re: Disappearing API docs Nigel Wade <nmw@local.domain> - 2016-07-20 17:10 +0100
Re: Disappearing API docs Eric Douglas <e.d.programmer@gmail.com> - 2016-07-20 10:39 -0700
Re: Disappearing API docs Eric Sosman <esosman@comcast-dot-net.invalid> - 2016-07-20 13:59 -0400
Re: Disappearing API docs Eric Douglas <e.d.programmer@gmail.com> - 2016-07-20 11:08 -0700
Re: Disappearing API docs Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-20 21:55 +0000
Re: Disappearing API docs Eric Sosman <esosman@comcast-dot-net.invalid> - 2016-07-20 18:19 -0400
Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-22 13:31 -0400
Re: Disappearing API docs Nigel Wade <nmw@local.domain> - 2016-07-21 10:08 +0100
Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-22 13:30 -0400
Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-22 13:16 -0400
Re: Disappearing API docs Gene Wirchenko <genew@telus.net> - 2016-07-22 15:24 -0700
Re: Disappearing API docs Lew <lewbloch@gmail.com> - 2016-07-22 15:34 -0700
Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-22 19:29 -0400
Re: Disappearing API docs Gene Wirchenko <genew@telus.net> - 2016-07-23 21:45 -0700
Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-30 22:33 -0400
Re: Disappearing API docs Gene Wirchenko <genew@telus.net> - 2016-08-02 11:07 -0700
Re: Disappearing API docs Eric Sosman <esosman@comcast-dot-net.invalid> - 2016-08-02 14:26 -0400
Re: Disappearing API docs Gene Wirchenko <genew@telus.net> - 2016-08-02 15:53 -0700
Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-08-03 21:55 -0400
Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-19 20:43 -0400
Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-19 20:40 -0400
Re: Disappearing API docs Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-20 11:45 +0000
Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-20 08:47 -0400
Re: Disappearing API docs Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-20 18:44 +0000
Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-19 20:24 -0400
csiph-web