I need some simple logic (simplest possible.) to test for tile requests that
are "bad", out of range or simply badly formed.
Im using the url template within the api, something like this:
myURL/tiles/{X}-{Y}-{Z}.png
The tile server basically tries to retrieve a tile if it already exists in
the cache, and generates it "on the fly" if its not in the cache.
Now, Im worried that people might eventually maliciously try to access this
url directly, passing it junk parameters just to slam the server.
Does anyone have any advice on simple logic to keep this from happening?
Note: I don't need code, I need an algorithm (though Id be doing this
testing in php).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Maps API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Maps-API?hl=en
-~----------~----~----~----~------~----~------~--~---
