The urls sent to our redirect.html page can be munged by either browsers and/or bots and it causes our tokenization of a metrics integration request to get out of whack and it causes an exception.

Here are two example records that cause problems:
2017-11-07 00:13:32 0.003 302 https "www.earthsystemgrid.org" /redirect.html link=http%253A%252F%252Fwww.narccap.ucar.edu%252F'" "0" - 202.78.202.108 "guest" - -

2017-10-31 20:40:34 0.005 302 https "www.earthsystemgrid.org" /redirect.html link=http%25253A%25252F%25252Fwww.anl.gov'%22 "0" - 185.41.186.236 "guest" "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; iebar; InfoPath.2; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)" -

Notice the the extra single quote or single and double quote at the end of the link query parameter.

It is those quotes that is causing the problem because the above strings will get tokenized into 15 tokens instead of the expected 13 or 14 tokens.