Quote from: kslavik on October 20, 2013, 08:14:09 PM

Quote from: Jriker1 on October 20, 2013, 02:52:37 PM

Any update on the JSON? Not sure if my PM'd IP was added to the exception list. I am noticing Incapsula is screwing everything up? See the custom CAPTCHA page you were telling me about but obviously can't enter the code when it's a vendor's webserver. I have 6 miner systems and need this feed to monitor what my individual machines are doing as the standard website shows for each coin what each miner is doing (if one machine has 3 cards and each mining a different coin, each worker shows 3 times) and I've consolidated it in various ways to know easily if a miner has stopped. Even getting 404 error iframe boxes on the screen when it's trying to connect. When I do a refresh of the page, the URL changes to.

http://localhost/_Incapsula_Resource?CWUDNSAI=23_06D98857&incident_id=133000630312744962-1253996524770493430&edet=12&cinfo=180db217c753818f04000000

I am trying this on my local computer which is on my personal network to eliminate my hosting provider from the issues. Which apparently shows Incapsula is mucking things up. I have tried my thought of passing a user agent but doesn't do anything. Guess just like other acts of terrorism, if you want to call a DDOS attack terrorism, they are winning. Making our lives more difficult to deal with. Sorry to go all philosophical but for me a deal breaker. Not really your problem Flound if there is no way around it to protect yourself but what you gonna do.

FYI: Can't tell date of the thread, but looks like a common issue with this protection: http://www.enjin.com/forums/m/10826/viewthread/4539356-accessing-enjin-api-through-php-gives-404-or-redirect

Thanks.

JR

I was given a private IP by Flound which did work for my API reader. But this is not a permanent solution to redirect everybody to a private IP address to use an API. API pages cannot be protected by Incapsula, because it is intended to be used between a browser and a website. API on the other hand is not accessed from the browser most of the time but rather it is access by some script (unfortunately DDOS attacks are done by the scripts as well) . So the error messages should not be in HTML but they should be in JSON as API is using json as an output.

I see cryptsy is using a separate domain/IP address for its API for the reasons listed above.

I'll spin up api.multipool.us with a limited number of Apache sessions (10 or so) as soon as I can.