Ted Powell (ted@eslvcr.fireplug.net)
Sun, 15 Aug 1999 15:12:52 -0700
On Fri, Aug 13, 1999 at 07:28:46PM -0700, Randall Clark wrote:
>
> I was able to access my users dirs off one of my linux webservers using
> this;
>
> http://www.domainname.com/~username
In normal circumstances, /home/username/public_html (or equivalent) is
a directory, not an ordinary file, which means that a URL referencing
it must end in a '/'.
Most of the time, one can get away with leaving off the slash, at the
expense of sitting and waiting while the web server tells the browser,
"No, there's no ordinary file by that name. Try again with a '/' on the
end.", and while the browser resubmits the request with the '/' appended.
After the page has come up, look in the browser's Location (aka Address)
field, and you will see that the final '/', that you didn't provide,
has now been added.
Except over a really fast link to a really fast server, it takes less
elapsed time for the browser user to simply type the slash in the first
place than it takes for the extra network transactions while the server
and the browser sort out the user's mistake.
> now I can only access it this way ( Notice the " / " at the end.
>
> http://www.domainname.com/~username/
>
> What gives?? is their a way to fix this ??
As described above, this is the correct way. Apparently you have changed
something so that recovering from the missing '/' no longer works.
Try doing diffs between your original configuration files and the
current ones. You did save copies of your original configuration files,
didn't you?
--
(o- ted@psg.com http://psg.com/~ted/ (Ted Powell)
//\ The source is out there,
v_/_ and it's freely downloadable.
This archive was generated by hypermail 2.0b3 on Thu 09 Sep 1999 - 06:40:34