TerraFrost wrote: If they're encountering the problem at login, then this MOD, quite simply, isn't to blame.
The problem was resolved the moment I removed the MOD. Draw your own conclusions.
TerraFrost wrote:I have no idea either, but my server logs confirm it.
Your server logs confirm that they're getting an "unable to scan for proxies" error message? All my own server logs log is the HTTP request, not including POST data, or COOKIE data.
No, my server logs confirm that the user triggered the MOD when merely trying to login, and the logs further confirm that the same user logged in successfully immediately afterwards via a proxy website.
TerraFrost wrote: Your understanding is correct. There's no way, without modification, for this to be triggered during the login process.
If you say so. I'm curious what other explanation there might be for the source of an error that says 'error scanning for proxies', if it's not the proxy scanning MOD that, upon removal, caused the problem to be resolved.
I'm no expert, but to me it's pretty straightforward: Proxy Scanning MOD = proxy scanning error; NO Proxy Scanning MOD = NO proxy scanning error. Conclusion: the Proxy Scanning MOD caused the proxy scanning error to occur, somehow. I personally like that better than the "magic missile spell" theory.