On Sat, Nov 30, 2013 at 2:53 AM, Borden Rhodes <jrvp@xxxxxxxxxxxxxxxx> wrote: > Thank you, Tom, for your response and explanation. > > My understanding of the HTTP is pretty simple. I'm doing some research > on the protocol as the second part of your answer is somewhat over my > head. I follow (I think) that httpd considers each request separately > to any other request (so, if httpd receives a GET for an HTML file and > then a GET for a PNG, it doesn't infer that the PNG is to be displayed > in the HTML file). What I don't quite follow is why httpd can't be > told to spot an incoming request for one location and fetch a file at > another. > > To see where my understanding is falling apart, I hope you will humour > me with an abstracted exchange between the client and server in my > situation: > 1) Firefox to httpd: GET http://localhost/ClientWork/Drupal/ Browsers usually connect to localhost and ask just for /ClientWork/Drupal/. ... > > Assuming that the above steps accurately represent the exchange > between Ff and httpd, am I to understand that there's no way to tell > httpd in a .htaccess file at step 3 that a request in the form > http://localhost/s/d/f/i/... should look for the file at > ~/www/CWD/D/s/d/f/i/... ? You can do that with just Alias if there's no dynamic part. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|