Trivial question: Why does tracd reject a request requiring the user to be logged in with a 403 HTTP error (Forbidden), rather than with a 401 HTTP error (Unauthorized)? I'm sure there is a valid reason to do so, but I can't remember why.
As RFC 2616 specifies in section "10.4.4 403 Forbidden" that "The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated.", it means that a client will not try to send an authentication request to log in. How to get command-line tools such as wget or curl working with tracd when the requested URL points to a resource which requires authentication? Thanks, Manu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
