4 ms·
What browser, and what did you do to get that error? Like, were you just searching? Did you try something crazy like leaving the field empty? EDIT: Was able to
by finnn 11y ago
What browser, and what did you do to get that error? Like, were you just searching? Did you try something crazy like leaving the field empty?
EDIT: Was able to reproduce. I'll investigate.
- jzig 11y agoNormal search. Chrome 44.
- finnn 11y agoSeems to be an issue with namecheap not returning any results and my end not having good error checking. I'll see what I can do to fix
- grepper 11y agoYes, looking at the network requests I also get this error fairly consistently by the third or fourth batch: > {"ApiResponse":{"$":{"Status":"ERROR"},"Errors":[{"Error":[{"_":"Too many requests","$":{"Number":"500000"}}]}],"Server":[""],"GMTTimeDifference":[""],"ExecutionTime":["0"]}} Which then results in "Uncaught TypeError: Cannot read property '0' of undefined". Cool idea, though!
- finnn 11y agoDamnit, namecheap. They must be ratelimiting me... I didn't see anything about ratelimits in the API docs, I guess I'll go re-read them
- dspillett 11y agoI would assume any API like this would have rate limits of some sort. If you are making a separate request for every TLD that is likely to be worse too.