| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 13
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I hear you -- my guess is it's that my IP address is cookied somewhere in a session in a load balancer, making me "sticky" to whichever node isn't working right. I've saved off my reply to a notepad and will come back to it tomorrow, in theory after any sessions have sticky timed out then see from there...
|
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges:
|
@xithryx: I had the same 403 Forbidden problem several months ago and found the root cause. If you're able to search my post history, it should be in there. Has something to do with text input validation -- some string in your post caused it.
----------------------------------------Edit: Found it. If you read this post and the next post, the text string that was causing the 403 was / etc / so I got around it by adding spaces.
[Edit 1 times, last edit by hchc at Aug 26, 2018 1:09:18 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
@hchc thank you for the hint! It turns out it's the combination of "slash-etc-slash" with the second slash being the key - spaces around it don't matter, you cannot seem to have the string of those 4 characters in direct order either alone or with other content, nor in code blocks. Kinda cumbersome, being one of the key/main directories in every UNIX/Linux based system but I suppose the forum team has their reasons.
EDIT: as I type you updated too, thanks kind stranger - we're on the same wavelength, exactly what I found |
||
|
|
|