Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21bf7560f26d945

Jump to content

Talk:HTTP 403

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 8 months ago by Stevebroshar in topic Redirect

IP blacklisting

[edit]

Shouldn't IP blacklisting be somewhere on here? I think that displays error 403. by kaiete (talk) 17:37, 21 November 2020 (UTC)Reply

untitled

[edit]

The 403 or Forbidden error message is an HTTP standard response code indicating that the client was able to communicate with the server, but the server doesn't let the user see requested. 403 errors should not be confused with "Forbidden. You don't have permission to access / on this server." or similar errors, in which a pass to the destination server cannot be made at all. HYHU  Preceding unsigned comment added by 113.189.101.4 (talk) 06:22, 11 July 2017 (UTC)Reply

don't have permission

[edit]

for the sentence 403 errors should not be confused with "Forbidden. You don't have permission to access / on this server." or similar errors, in which a pass to the destination server cannot be made at all. I was always under the impression that the error code for that was 403 as well. Bawolff 01:00, 16 February 2007 (UTC)Reply

It is. I've removed it. -- Jon Dowland 15:34, 5 March 2007 (UTC)Reply

Decimals?

[edit]

I seem to remember getting an Error 403.5 at one point... could this be explained by someone with a meaty brain? ThatOneGuy 21:16, 18 February 2007 (UTC)

see Talk:List of HTTP status codes. Bawolff 01:07, 19 February 2007 (UTC)Reply

Security

[edit]

Maybe add a section about the security (or lack thereof) of using this error code for permission errors? (i.e. It lets the client know such a resource exists, which may pose security issues.) —Preceding unsigned comment added by Pyrosphere (talkcontribs) 01:04, 2 April 2010 (UTC)Reply

THIS. 403s are a security risk. It blows my mind that we're a decade down the road, and there is nothing about this matter. 96.69.209.233 (talk) 20:57, 21 March 2019 (UTC)Reply
A. May be lack of computer expert AND wiki editor interested in adding that to this wiki article. B. May be lack of WP:reliable source as a citation to fulfil WP:V requirement or C, WP:trivia to mention. Matthew hk (talk) 21:15, 21 March 2019 (UTC)Reply
A 403 means the bad guys have already logged in. Changing it to something else is just Security through obscurity. Q T C 15:47, 4 June 2024 (UTC)Reply

Redirect

[edit]

This article is very short since the topic has little to it. Also, the title (HTTP 403) is not a notable term. If you know what HTTP is, then you know what the title refers to. But, a title is supposed to be a notable term. This is not. Something like 403(HTTP response status code) would be more appropriate. But... let's merge this into list of HTTP status codes where most other codes already live in peace and harmony. ... Done. Stevebroshar (talk) 15:16, 19 November 2025 (UTC)Reply