200 X-Frame-Options: SAMEORIGIN Content-Security-Policy: frame-ancestors 'self'; X-UA-Compatible: IE=Edge X-XSS-Protection: 1; mode=block X-Content-Type-Options: nosniff X-Telligent-Evolution: 12.x Pragma: no-cache Connection: close Accept-Ranges: bytes Cache-Control: no-store, no-cache, max-age=0 Date: Sat, 30 Nov 2024 02:33:29 GMT ETag: "0x8DD02F56CCD7D1F" Set-Cookie: .te.csrf=WUZXvlx-rT0BYC9F-3jjGQ2Ew6ZLnvZh2J28Ia4oWRo; path=/; secure; SameSite=Lax Set-Cookie: .te.auth=Y397WS1cARzLxSUW%2bIEx4WxcpwgkZBiiiDCsd3zmTNR%2fZcpBa%2fk6YoPIUlgO6XA4XDUVn5LV9jfzkNdrV44gx2gvGdhzzTmwx21theon6K2nfMT50%2fzjnl0LkwsVadtYJBDumN1vEvFNGcOCkcORfBKGJr1g5HLsH9VIXM9%2bH2IEQru43gtGh7FJLAlyCpCVBol%2fnqnlnJYUYR%2fQHETy13TQJ4Auqh22uNeIR%2bEI9FxT1YCjPZIY0ZRLcs6PxmaMvICvDTvBUNa8L98RlT8wIA%3d%3d; path=/; secure; HttpOnly; SameSite=Lax Set-Cookie: e14Guest=1; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Country=NL; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Language=en; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14TimeZone=Etc/UTC; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Server-Timing: cdn-cache; desc=MISS Server-Timing: edge; dur=7 Server-Timing: origin; dur=20 Server-Timing: ak_p; desc="1732934009586_34849654_148082019_2767_7610_6_9_-";dur=1 Strict-Transport-Security: max-age=86400 ; includeSubDomains ; preload #set ($UserId = $core_v2_user.Accessing.Id) #set ($Roles = $core_v2_utility.MakeList('Moderators', 'Almost Admins', 'Administrators')) #set ($IsAdminLike = $e14_utils.IsUserInRoleOrAdmin($UserId, $Roles)) #if($IsAdminLike == 'False') #end
Actions
Forum Thread Details
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 12 subscribers
  • Views 712 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

'Blogs' tab is sick again

shabaz

Hi,

The 'blogs' tab is generating just three pulsing circles again. I've tested on home and mobile internet connections, with two different browsers, and I see the same problem.

Top Replies

  • +1

    This was me (again) Shabaz.

    We've got some automated defense against SQL injection attacks and JS attacks in place, and it keeps firing against blogs because they contain code. When you get hit by it, it'll affect all browsers from the on IP. 

    It's taking some tweaking. Previously when you had this it was a minor tweak, but I think this time I'll need to use something a bit heftier.

    This is one of those things where if I do my job right, then nobody should notice, but if I get it wrong, I get everyone come down on me!

  • 0 in reply to Dudley

    Hi Dudley,

    Oh, odd.. I used two different connections, one was wired (VDSL) and the other was cellular (4G/5G), but the tab didn't work on either when it occurred. 

    I'll double-check next time it occurs, to confirm. I switch off the WiFi on the mobile phone, when I was doing the comparison.

    Many thanks for investigating!

  • 0

    Hi all,

    At time 21:05 UK-time 29th Sep, the blogs tab failed to load again (when using DSL), on my laptop. (EDIT: it's now 21:16, it's failing for ten minutes at least).

    As soon as this occurred, I switched off the WiFi connection on the mobile, and tried browsing to the Blogs tab using mobile Chrome. I see the same issue, so it can't be security measure related. 

    I used the whatismyip website to confirm I had a very different IP address (86.xx.xx.xx on laptop, and 148.xx.xx.xx on phone).

    Please can this issue be re-opened, because it doesn't seem to block on IP. I can supply the IP addresses if it needs to be checked against any log.

  • 0 in reply to shabaz

    Was failing for me at that time as well.

  • 0 in reply to Andrew J

    Thanks for confirming! I guess it can't be the automated defence stuff then. Plus it seems frequent (since it last sick no later than three days ago at least).

  • 0 in reply to shabaz

    Pretty sure it was broken this morning as well, I can’t really remember.

  • 0 in reply to shabaz
    shabaz said:
    Please can this issue be re-opened, because it doesn't seem to block on IP. I can supply the IP addresses if it needs to be checked against any log.

    I'm also not convinced we've definitely identified the problem, but it's definitely something more server-side related.

    Though we cannot necessarily show everything 'behind the curtain' to how the protections determine someone's being sinkholed regarding this, it would possibly work across different IP addresses, there's an element of fingerprinting that goes on.

    That isn't to say that people shouldn't complain about it still happening, that's helpful, and to know what dates/times/timezones it happens, so thank you.

  • 0 in reply to shabaz

    I've found you in the logs. I can see what has happened but I can't answer why it has happened.

    It's based on a piece of content you both viewed which is throwing a false positive.

    It's late now so I won't do it now, but in the morning I'll pull that module.

  • 0 in reply to Dudley

    I've looked again today with a wakeful mind, and I can see what happened here, and made a small tweak.

    Can you shout loudly if you get this again   &  

  • 0 in reply to Dudley

    Will do.  Makes us sound a little dodgy actually Grinning : can you not explain more about what the issue is?

  • 0 in reply to Dudley

    Awesome, will do, thanks!