Forum Post: 403 Forbidden nginx 0.7.67 workaround
Posted 13 years ago on Oct. 27, 2011, 3:40 p.m. EST by ARod1993
(2420)
This content is user submitted and not an official statement
I'm not sure why, but something screwed up the redirect system. What you need to do to get around it is this:
A standard comment permalink url looks like this:
http://occupywallst.org/forum/name-of-thread/#comment-xxxxxx
A standard redirect link from a notification looks like this:
http://occupywallst.org/notification/xxxxxx/.org/forum/name-of-thread/#comment-xxxxxx
As you all can see, the redirect link included in the notification system contains some extra things that tell the server that you're going to the comment from a response notification rather than directly, and it's that extra stuff that's causing the problem. Just go into your browser bar and delete the extra stuff until the URL looks like the example comment permalink I wrote above, hit Enter, and you're good.
Thanks! I wish you would have figured this out earlier. It's working for me.
No problem!
Jump.
It worked for me; is it working for everyone else?
Yep...that is the fix that was identified earlier, and haven't seen anything about it not working for someone.
http://www.occupywallst.org/forum/work-around-for-anyone-getting-that-403-forbidden-/
Gotcha; I didn't see Johnnyguy's post when I put this up here so I wasn't sure. Thanks, though! I think we need to bump either this or JohnnyGuy's thread on a regular basis until the problem goes away.
No problem, in fact I copied a link to this thread as I think your explanation of the work around will help the less technically inclined.