Buy

Books
Click images for more details

Support

 

Twitter
Recent comments
Recent posts
Currently discussing
Links

A few sites I've stumbled across recently....

Powered by Squarespace

Discussion > Thread for 403 error tests - not intended for comments but feel free

... it posts.

So it seems if you get 403'd you can post immediately (without preview) by:

A. Clearing history (cache and browsing history) OR B. Getting a new IP address.

(or both, presumably)

I'll see if something similar works for Preview. I doubt it but...

Nov 27, 2015 at 7:19 PM | Unregistered CommenterMartin A

No. That would have been too easy.

I tried [preview] [clear recent history] [edit] and got 403.

Nov 27, 2015 at 7:24 PM | Unregistered CommenterMartin A

checking

Nov 27, 2015 at 7:25 PM | Unregistered CommenterMartin A

I just got 403'd. I'll try reposting WITHOUT clearing recent history

Nov 27, 2015 at 7:26 PM | Unregistered CommenterMartin A

that worked. So perhaps 403's are getting less deadly?

Nov 27, 2015 at 7:27 PM | Unregistered CommenterMartin A

I just got 403'd. So now another repost without clearing history

Nov 27, 2015 at 7:28 PM | Unregistered CommenterMartin A

So that worked too. So it seems that you can now post after a 403 without changing IP address and without clearing history....

So the behaviour of 403's has changed, it seems. Previously you got one and were locked out for a long time.

Nov 27, 2015 at 7:31 PM | Unregistered CommenterMartin A

It's mutating. Is this the birth of computer based life?

Nov 27, 2015 at 7:50 PM | Unregistered CommenterTinyCO2

Did I get that right?
Nov 27, 2015 at 7:02 PM | Unregistered CommenterMartin A

Martin, in step 3 I think, if I recall correctly, that I did not reload the discussion page, but pressed the back arrow in the browser to lead back to the typed message in the dialogue box, and clicked on "create post"

Nov 27, 2015 at 8:08 PM | Unregistered Commentermichael hart

OK. So I just attempted a test with 1 preview.
The preview worked, but failed to post, with a 403.
I pressed "back" in the browser.
Then cleared browser history (chrome).
Clicked on edit to write this message.
Then clicked create post.

Nov 27, 2015 at 8:16 PM | Unregistered Commentermichael hart

I just tried another post, clearing history before the preview, and couldn't post.
Going back and clearing history, then editing the message, also failed.
Further back attempts led to a form-resubmission error. No way out in any direction.
So I closed window and created this in a new window, reloading the discussion page, cleared history, and posted without preview.
Interestingly, the auto-complete then required me to fill in my author name information again, which is a fairly rare occurrence for me.

Nov 27, 2015 at 8:39 PM | Unregistered Commentermichael hart

As stewgreen noted earlier, it also seems that the lock-out period may have been changed from what was (for me and him, at least a couple of hours). My guess is that maybe squarespace are just trying to to "shim" several parameters?
As you point out earlier, Martin, if they don't understand how genuine users at BH normally interact with these parameters then it would simply end up being a matter of trial and error. Except than now they have genuine users at BH possibly changing their 'normal' patterns as a result of sqarespace tinkering. If they told us how it works then we could avoid recursion.

Nov 27, 2015 at 8:47 PM | Unregistered Commentermichael hart

michael - I had some exchanges with Squarespace including detailed screenshots. I suggested that they try posting themselves here instead of relying on my telling them what happens but they explained that they are not allowed to. Anyway they also said that they think they have solved the problem and will be rolling out a corrected system.

Sounds promising, though my nature is to believe things when I see them.
______________________________

OK - I just did a preview/edit WITHOUT getting 403'd.

Nov 28, 2015 at 8:38 AM | Unregistered CommenterMartin A not logged in

OK - perhaps it has gone for good. Let's see...

I just did about ten preview/edits without a 403.

Nov 28, 2015 at 8:40 AM | Unregistered CommenterMartin A not logged in

#1

Nov 28, 2015 at 8:40 AM | Unregistered CommenterMartin A not logged in

got a 403.

Nov 28, 2015 at 8:42 AM | Unregistered CommenterMartin A not logged in

but then without changing IP address and without clearing any history, it let me post. So it is still there but less obtrusive.

Nov 28, 2015 at 8:43 AM | Unregistered CommenterMartin A not logged in

B

Nov 28, 2015 at 8:44 AM | Unregistered CommenterMartin A not logged in

and another 403. But reloading BH, discussion, thread for 403 errors...

Nov 28, 2015 at 8:46 AM | Unregistered CommenterMartin A not logged in

so it appears less frequently and does not lock you out for hours.

Interestingly, the auto-complete then required me to fill in my author name information again, which is a fairly rare occurrence for me.
Nov 27, 2015 at 8:39 PM | Unregistered Commentermichael hart

Is that the result of clearing history, perhaps?

Nov 28, 2015 at 8:48 AM | Unregistered CommenterMartin A not logged in

OK. Logged in, new IP address. Let's see how many posts are needed to get a 403.

#1

Nov 28, 2015 at 9:52 AM | Registered CommenterMartin A

#2

Nov 28, 2015 at 9:52 AM | Registered CommenterMartin A

that did not take long. 403 on third posting

Nov 28, 2015 at 9:54 AM | Registered CommenterMartin A

But I can immediately post again evidently

Nov 28, 2015 at 9:55 AM | Registered CommenterMartin A

#2

Nov 28, 2015 at 10:00 AM | Registered CommenterMartin A