Normally, when my server gets an invalid sessionID on the url it rewrites it. However (several?) search engine(s) are sending requests to my server with a lower case in the session number, where there is normally an upper case S. So for example
(s(vou3fq454gk3fbrncrmk1bmj)) will not just rewrite the sessionID and keep going, but
(S(vou3fq454gk3fbrncrmk1bmj)) WILL rewrite the sessionID and keep going without an error.
This is filling up my database and making it hard for me to use it effectively, plus, I would just like it to work.
Is there any way for it is not care if that first '(s(' is lower case? Or is there a way for IIS to cope with this in an efficient manner?
Thanks for any suggestions.
View Complete Post