> Then the only solution is session-management. Forget about basic auth,
> login over HTTPS with an HTML form which is handled by something on the
> server-side (eg PHP). Once validated, give the client a cookie and
> redirect him to the HTTP section. It's not trivial, unfortunately...
Ok, thanks another time, I try to use cookies with php.
>>
>> > Does /path/to/webpage/1/2/4 exist?
>>
>> Yes, I'm sure. But, one consideration: doesn't is inside
>> server root the
>> path, for example, is "/usr/share/", and it have the correct
>> permisions.
>
> When I say "/path/something..." I mean a real filesystem path - something
> you can do "ls" on. Nothing to do with relative to ServerRoot. So to
> rephrase the question, what happens when you do:
>
> ls -l /path/to/webpage/1/2/4
When I execute:
ls -l /path/to/webpage/1/2/4
I see the content of the directory, the directory exist.
I'm rephrase the question too... when create an alias, for example (using
real pathnames):
Alias /foo "/home/especial"
<Directory "/home/especial">
Options None
AllowOverride None
Order allow,deny
Allow from all
</Directory>
And type http://my.server/foo (typing: http://my.server/foo/index.html
return the same) server returns not found... In directory /home/especial,
I have an index.html file.
>> > what's in the error_log
[error] [client 123.123.123.123] File does not exist: [error] [client
123.123.123.123] File does not exist: /var/www/foo
> I'm getting mixed up - I know you don't want to post your real path names,
> but you're using the "/path/to/.." shorthand inconsistently and now I
> don't know what you mean. Please post again:
I try to post totally consistently ;)
> - the Alias directive
In this case isn't an alias, I only need list a content of this directory,
see that:
<Directory "/var/www/ftp">
Options Indexes
AllowOverride None
Allow from all
</Directory>
> - the error log entry
123.123.123.123 - - [15/Apr/2005:22:18:34 +0000] "GET /ftp/ HTTP/1.1" 403
339 "-"
> If you replace anything with "/path/to/..", replace exactly the same way
> in both lines.
Don't worry, I never post again with "/path/to/..." ;)
> This is correct, but because of the "/path/to/.." confusion, I no longer
> know if "/path/to/list" is a real filesystem path (it should be) or a
> URL-path (which would be wrong). In any case, what do you get in the
> error_log when you try to access this directory?
I think now it's more clear...
Thank's! Nan.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|