Jump to content

Primary: Sky Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble
Secondary: Sky Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble
Pattern: Blank Waves Squares Notes Sharp Wood Rockface Leather Honey Vertical Triangles
Photo

My Follows' RSS throws 503 Errors on RSS readers?


  • Please log in to reply
7 replies to this topic

#1
deltarayedge

deltarayedge

    Potato Sprout

  • Members
  • 4 posts

http://www.feedvalidator.organd whatever RSS readers I can test are giving 503 errors. Attached File  firefox.png   2.69KB   0 downloads

But the feed runs fine inside browsers. Tested on Chrome and Firefox.

 

Any ideas?



#2
el0d

el0d

    Potato Sprout

  • Members
  • 9 posts
I've the same issue.  

It started happening right around the time I started seeing the page below when I'm accessing the website

post-151865-0-58108400-1511814249.png

 

So I'm kind of guessing this change might be the cause.

Attached Files



#3
metroid112

metroid112

    Potato Sprout

  • Members
  • 3 posts

It seems the website adopted a Cloudflare DDoS protection service because of a recent DDoS attack. Most apps that try to parse the Batoto website will need to update to work again properly.



#4
usage

usage

    Potato Sprout

  • Members
  • 6 posts

Blunt 503 on RSS feeds? Lol, c'mon.



#5
deltarayedge

deltarayedge

    Potato Sprout

  • Members
  • 4 posts

Should have guessed as much.

There's not many RSS readers that can solve the cloudflare javascript check, I don't know of any.



#6
WildCrow

WildCrow

    Potato Sprout

  • Members
  • 1 posts

Do the admins actually know that they can exclude the fucking RSS file/url from cloudflare ? because im not checking EVERY single series manually, that's what RSS is for.


Edited by ROTFLMAOMAGNETS, 28 November 2017 - 09:48 AM.
moved from thread #28178


#7
Grumpy

Grumpy

    RawR

  • Administrators
  • 4,078 posts
  • LocationHere of course!

The guess that the ddos protection is causing rss feeds to break is correct. The feeds work through bots that keeps on fetching data and the protection is designed to filter out bots.

 

But in the big picture, the problem is not the protection but that we're getting ddosed. The nature of the cf's ddos protection is meant to be temporary in nature. It's designed only to be on when you're actively being attacked and removed once it's over. But it's not over, that's why we're at this stage.

 

I cannot just exclude rss from cloudflare. That would negate the entire point of it. Security is only as strong as its weakest point. If it allowed rss feeds to be unprotected while sharing infrastructure, they could simply attack there and shut down the website. If the attack goes for an extended period of time, I will have to create a new independent rss feed.

 

I apologize for the inconvenience. But blame the ddos'er



#8
lasgjkgkjasg

lasgjkgkjasg

    Potato Sprout

  • Members
  • 8 posts

Well that's extremely unfortunate.