Re: My Very Strange Webhost, SBI! -- Opinions, Please
On May 13, 9:22 am, Andy Dingley <ding...@codesm iths.comwrote:
Huh? Sorry, but case-sensitivity does not appear to be the issue
here. It's an interesting point you raise, which I note for my future
reference, thank you kindly, but I don't see how it applies to my
situation, since my file names are all lower-case, as was every
reference to them in my src attributes...an d besides, surely a webhost
should have provided for such matters anyway.
LOL -- SBI! as a cargo-cult! It's more true than not, yes...I was
actually thinking of that Heaven's Gate cult of suicidal UFO-believing
website designers from the '90s....
????
I apologize, Andy, but I know nothing about servers, so I'm not able
to place your remarks in a useful context vis-a-vis my situation...if
you don't mind, would you please do a step-by-step "chronology " of the
chain of events? I honestly don't know how to "parse" your
statements; I don't know how servers work and it sounds like you're
referring to how they work....
On May 13, 9:22 am, Andy Dingley <ding...@codesm iths.comwrote:
>
>
You know what that's caused by? Case issues in filenames. Sometimes "
" space characters in filenames not being encoded correctly in URLs
(although browsers usually compensate for that).
>
Your desktop is almost certainly Windows (case-insensitive filenames).
Your web server filesystem is almost certainly Unix (case-sensitive
filenames). Your web server is probably (unless they deliberately
change this) also case-sensitive in URLs.
>
So when you test with a local filename that has the wrong case, your
Windows system doesn't care and it all works.
>
You upload this to the server (now case-sensitive) and it fails.
>
You know what that's caused by? Case issues in filenames. Sometimes "
" space characters in filenames not being encoded correctly in URLs
(although browsers usually compensate for that).
>
Your desktop is almost certainly Windows (case-insensitive filenames).
Your web server filesystem is almost certainly Unix (case-sensitive
filenames). Your web server is probably (unless they deliberately
change this) also case-sensitive in URLs.
>
So when you test with a local filename that has the wrong case, your
Windows system doesn't care and it all works.
>
You upload this to the server (now case-sensitive) and it fails.
here. It's an interesting point you raise, which I note for my future
reference, thank you kindly, but I don't see how it applies to my
situation, since my file names are all lower-case, as was every
reference to them in my src attributes...an d besides, surely a webhost
should have provided for such matters anyway.
You talk to tech support, and you both talk yourself into this cargo-
cult
cult
actually thinking of that Heaven's Gate cult of suicidal UFO-believing
website designers from the '90s....
>that it's using an absolute path that's the trick. You get this
absolute path by browsing to the directory with the files in (through
the web server), seeing a list of file URLs (generated by the server,
so the case is correct) and you then copy and paste one of these.
absolute path by browsing to the directory with the files in (through
the web server), seeing a list of file URLs (generated by the server,
so the case is correct) and you then copy and paste one of these.
Two things have happened: you've switched from relative to absolute
(obvious, but unimportant) and you've also corrected the case of the
filename in the URL (easily ignored but crucial). _That's_ why "it
started working when you went to absolute paths".
(obvious, but unimportant) and you've also corrected the case of the
filename in the URL (easily ignored but crucial). _That's_ why "it
started working when you went to absolute paths".
to place your remarks in a useful context vis-a-vis my situation...if
you don't mind, would you please do a step-by-step "chronology " of the
chain of events? I honestly don't know how to "parse" your
statements; I don't know how servers work and it sounds like you're
referring to how they work....
Comment