Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If I have a resource that a requesting client doesn’t have access to but I want to notify them about an alternate resource for which they do have access, should I send them a 403 Forbidden with the alternate resource’s URI in the header or content? Or should I just send a 303 See Other redirect to the resource to which they have access?
There is no HTTP code for ‘forbidden but have a look at this’.
You can, however, customize your 403 error page so that a link to the alternative content is present. If you have multiple alternative links you might find this solution better.
If notifying the user that access is denied is not that important you might want to use a 302 (temporary redirect) instead or, if the user will never have access to the forbidden content, a 301 (permanent redirect).