At 23:23 +0530 7/19/10, Tapas Mishra wrote: >On Mon, Jul 19, 2010 at 10:51 PM, Dan Poirier <poirier@xxxxxxxxx> wrote: >> Try it and see. >What do I try and what do I see can you be a bit more specific. >I have developed websites and used Apache to host cloud applications. Programming by experimentation is one of the things that makes for incompatible code. Apache is not proprietary software and it shouldn't be a requirement. a request for http://www.myexample.com/site/css/some.css will be treated by the domain name server system as machine www at domain myexample.com which has a unique IP address as a number stored in .com. When Apache gets the HTTP request it will look up the DOCUMENT_ROOT specified by the user whose instance of Apache is running. The page to be served will be identified by effectively changing the working directory to DOCUMENT_ROOT after which the site/css/some.css file will be delivered. /var/www//site/css/some.css is misleading because of the doubled up slashes. Such things can have special meaning such as returning to the system root before processing what follows. It's likely that an unprivileged user like wwwuser will not be allowed to do that. Was the // a typo? The whole bit of declaring variables like DOCUMENT_ROOT with and without a leading slash and ending URL's with a slash when you want a directory listing remains a bit enigmatic. Following the leads in a .config file is best. In an scp operation intended to deliver a document to your space on the server the // construct can be useful. And. . . I'm no expert. Please change anything that's wrong for the rest of us. -- --> A fair tax is one that you pay but I don't <-- --------------------------------------------------------------------- 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
|