Performance Considerations

Some browsers do not send user credentials for a request until challenged. For these browsers, the sequence of events on every request for a protected file is:

send request receive authorization required response resend request with authorization information receive file

This happens for protected every file. Therefore, for best performance, only place files in protected areas that need the protection of an authenticated user session. This way extra trips to the server and authentication processing is minimised.