Daniel L. Miller wrote: > I'm still not clear on what redirection does. In this instance, seems > like most requests are supposed to be redirected to index.php. I guess > I'm looking for clarification on what actually happens between the > client and server on a redirection. > > For example, say the client asks for "myserver.com/something.jpg". With > the redirection rule, does the server internally decide to call > "index.php", and tell it the original request was for "something.jpg"? > Or does the server tell the the client to re-send the request, but ask > for "index.php" instead? I'm sure I'm greatly complicating what should > be a simple action, but for some reason my tiny brain doesn't want to > grasp this.
You're this >||< close to figure it out all by yourself, but I'll still help you with that one. :) You have two types of redirection, internal and external. Internal is your first case, server decides to call something else internally and send the result back to browser, without browser ever knowing that the request was rewrited/redirected in the background. External type works the opposite way, in that case server sends HTTP redirect status code to browser asking (forcing) it to go to another URL to get the needed information. Hope this clarifies things a bit, this piece of Cherokee is extremely simple and well designed. But, of course, very powerful when you know what you're doing (though takes some time to practice it, i know first hand :)). -- http://www.linuxinsight.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
