Fictionmania error 429 come back tomorrow????

A word from our sponsor:

The Breast Form Store - NEXT TO PERFECT - NOW ON SALE

Submitted by on

Printer-friendly version

Author: 

I have suddenly started getting Fictionmania 429 errors and it tells me to come back tomorrow????
Has anyone else seen this?

Click Like or Love to appropriately show your appreciation for this post:

Comments

Working for me...

Submitted by on

erin's picture

Can you clear your browser cache and try again?

Hugs,
Erin

= Give everyone the benefit of the doubt because certainty is a fragile thing that can be shattered by one overlooked fact.

Browser cache

Submitted by on

Clearing the local browser cache is NOT the solution. Because the server will continue to send the same response, since that IP address has already exceeded the limit of requests for that day.

The only solution is to cool your heels and wait for 12 to 24 hours, so that the server can reset the request counter for your IP address.

Please see my comment below.

Fictionmania "moving to another server"

Submitted by on

I don't get an HTTP error, but fictionmania.tv shows a single page with the message

Fictionmania is moving to a new server and will return soon.

and any URLs pointing into the site (e.g., http://fictionmania.tv/searchdisplay/new7.html) fail with a 404.

The reason for the 429 error

Submitted by on

According to the RFC6585 the HTTP response code 429 is a client error. The explanation is:

429 Too Many Requests (RFC 6585)

The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes.

In other words, the number of page requests — even page refreshes — from your [public] IP address has exceeded a certain limit imposed by the server, usually within the current day in the server's timezone.

To resolve the issue/error you just need to wait for the controlling time period to expire. The easiest way is to wait 24 hours, and the issue should resolve itself.

When Fiction Mania responds with a 429 error, the error page gives the reason for that error. The message states:

429 Too Many Requests

Try again tomorrow

So the server is trying to prevent attacks and also even out the load and bandwidth usage.