• The forum upgrades have been completed. These were moderate security fixes from our software vendor and it looks like everything is working well. If you see any problems please post in the Forum Technical Support forum or email us at forum_moderator (at) aawforum.org. Thank you
  • Congratulations to Bernie Hyrtzak, People's Choice in the January 2026 Turning Challenge (click here for details)
  • Congratulations to Matt Carvalho for "Red Mallee Folded Form" being selected as Turning of the Week for February 9, 2026 (click here for details)
  • AAW Symposium demonstrators announced - If the 2026 AAW International Woodturning Symposium is not on your calendar, now is the time to register. And there are discounts available if you sign up early, by Feb. 28. Early Bird pricing gives you the best rate for our 40th Anniversary Symposium in Raleigh, North Carolina, June 4–7, 2026. (There are discounts for AAW chapter members too) For more information vist the discussion thread here or the AAW registration page
  • Welcome new registering member. Your username must be your real First and Last name (for example: John Doe). "Screen names" and "handles" are not allowed and your registration will be deleted if you don't use your real name. Also, do not use all caps nor all lower case.

403 Error

Bill Boehme

Administrator
Staff member
Beta Tester
TOTW Team
Joined
Jan 27, 2005
Messages
13,209
Likes
5,813
Location
Dalworthington Gardens, TX
Website
pbase.com
Has anybody else encountered Error 403 When posting an image to the Gallery, I encountered it several times this evening after clicking the submit button. Despite the error message the image posted without any problems.

Basically, the error means that the client (my browser) is wanting some forbidden resource. In this case it seems like a software error somewhere in PhotoPost or vBulletin. I would be interested in finding out if others are encountering the same issue.

Here is an excerpt from a description of the error code:
The web server thinks vthat the HTTP data stream sent by the client was correct, but access to the resource identified by the URL is forbidden for some reason. This indicates a fundamental access problem, which may be difficult to resolve because the HTTP protocol allows the Web server to give this response without providing any reason at all. So the 403 error is equivalent to a blanket 'NO' by the Web server - with no further discussion allowed.
 
Last edited:
Back
Top