OPEN Blackspigot HTTP to HTTPS Robot Verification Loop

[Guard15]

This is closely similar to https://blackspigot.com/threads/forward-http-to-https.17443/ since this happens sometimes.

Here is a video of proof: https://youtu.be/VbJBywEHoSs

Edit: While this may happen, I don't think it's on blackspigots end.

 

[Mango]

Ok? I have now clue why this happens.

I will inform higher ups now - INFORMED

UPDATE

I have just checked and the problem is not happening with me.
Have you tryed to connect to http://blackspigot.com/ directly and not
http: ... .com/threads/[THREAD NAME]

 

[Sauron]

It redirects to https for me.

 

[Guard15]

Ok? I have now clue why this happens.

I will inform higher ups now - INFORMED

UPDATE

I have just checked and the problem is not happening with me.
Have you tryed to connect to http://blackspigot.com/ directly and not
http: ... .com/threads/[THREAD NAME]

Yes, I have tried this without any page urls. But this was taken a minute before the site went into "maintenance mode" or something.

Proof: https://youtu.be/aj5-5uvvcZo

It redirects to https for me.

Yes, by default, it does the same for me. But lets say someone does try to view a page in basic HTTP. Like you said, you would be re-directed back HTTPS since that appears to be a site rule set on your CloudFlare console. But from what I can observe is that their appears to be 2 bot/-Redacted- protection pages upon when you first visit the site. By default, if you enter https://blackspigot.com in your browser, you would get this.

But if you enter in http://blackspigot.com you're faced with a Robot challenge. But trying to reproduce the problem is a bit hard to outline because of its sole difference between my phone and desktop. I made a video showing how the browser handles the site when switching between different protocols using my desktop.

Example Showcase: https://youtu.be/mWTFkqblTN4

For now, I am unsure how this problem appears to happen and I can hypothesize on a few parts that may be the reason, but for now I'll contemplate on if I should do more testing on this or not.