|
From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
To: "Web400@Midrange. Web400" <web400@xxxxxxxxxxxx>
Date: 11/21/2018 05:13 PM
Subject: Re: [WEB400] Setting up a web services server, and services
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxx>
Since the vast majority of IFS folders/files are case insensitive I
don't have to do anything to make it case insensitive - it just is
most of the time.
That's what I meant.
I know the standards say case-sensitive - but adherence to those
kinds of standards is not always a good idea. At least allow me to
specify otherwise.
Maybe I'm just feeling grumpy today - and I am surprised that google
has case-sensitive URIs. Just seems pointless.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Nov 21, 2018, at 12:38 PM, Nadir Amra <amra@xxxxxxxxxx> wrote:
This how applications are deployed in any application server. Nothing
new.u=http-3A__google.com_doodles&d=DwICAg&c=jf_iaSHvJObTbx-
Take for example, Google, which seems to operate a case-sensitive URL
policy on their own URLs. For example, the second link below is a 404:
INVALID URI REMOVED
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=-YMuzKF1npporl-PhLgByzXApm-
cnXdnxgsfz6TKWi4&s=cAAMWcwFn-CFYqX24pofo8-yHFtDtBeU7m98HBwCRvc&e=
INVALID URI REMOVEDu=http-3A__google.com_Doodles&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=-YMuzKF1npporl-PhLgByzXApm-
cnXdnxgsfz6TKWi4&s=Lcgk1Q5vsHJEruYKaC6EhsTIM7gLqrw9_CXHM94paqM&e=
Not sure what you mean about "....have to remember...". It has always
been the case.
RFC 3986 defines URIs as case-sensitive except for the scheme and host
tocomponents.
Having said that, one could always manipulate the HTTP configuration
lowermap URLs any way you want. So you could define you web services as
lowercase, then create a mapping such that any requests that come in is
cased before forwarding on to be processed.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.