profile page exceptions caused by malformed requests
if a profile page is loaded with an invalid url (e.g. : http://www.domain.com/?ctl=profile or : http://www.domain.com/?ctl=profile&userid= ), then an exception is logged. We need to ensure that this code is rewritten to add some defensive coding and not log erroneous errors.
Note: this is likely related to the spamming issue, hence why I am making it a 7.3.3 high issue
QA Test Plan
please log it as a different issue - we did fix this, but we also had a few pull requests for other variants, so your issue is either another variant or a few of those are clashing. If you can open up a new issue, and provide example url's that will help.
I was just about to open a bug that looks like it is related to this, and is reproducible on both 7.3.4 and the 7.4.0 beta. I have been getting a lot of exceptions in my logs, and occasionally crashed sites, it looks like some of these are caused by a "user" (I believe a spammer) trying to hit a profile page directly for a user id number that no longer exists. The result is 8 exceptions in a row (in 7.4.0) in the event log. If the "user" is not logged on they get a 404, if they are logged on they get a profile page for another userid (their own or next higher?).
I think this should be failing much more gracefully without all of the exceptions.
Cathel - Should this be reopened, or should I create a new bug?
This is verified fixed in Platform/Content/Enterprise 7.3.3 build 93