Error log: A potentially dangerous Request.Path value was detected from the client (:).

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
9 年 前
Hi,

I am getting this error showing on the log quite often, it relates to this CSS entry in jquery-ui-themes:

Full Message:  System.Web.HttpException (0x80004005): A potentially dangerous Request.Path value was detected from the client (:). at System.Web.HttpRequest.ValidateInputIfRequiredByConfig() at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)

Page URL:  /content/jquery-ui-themes/smoothness/data:image/gif;base64,r0lgodlhaqabaiaaaaaaap/yh5baeaaaaalaaaaaabaaeaaaibraa7

I am getting this alot on the log, should I be concerned, but more importantly, how can I stop it?  Aside from removing that line from the jquery-ui css manually?

Thoughts?

Thank you
9 年 前
Just to add, this is the line in the CSS it is referring to:

.ui-menu .ui-menu-item {
  margin: 0;
  padding: 0;
  width: 100%;
  /* support: IE10, see #8844 */
  list-style-image: url(data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7);
9 年 前
Just to add, this is for Nop 3.40
If anyone using 3.50 could confirm that they do not see this on their log... it would be greatly appreciated.

Thank you.
8 年 前
I'm having the exact same prob in 3.50. Also awaiting advice.
So - is it solved in 3.60? :P

(And NO, setting commonsettings.log404errors to false as recommended elsewhere doesn't solve the logging of this).
8 年 前
I'm getting same error in 3.5 ?
8 年 前
I have this issue in NOP 3.60
8 年 前
Nop 3.40

Page URL:  /content/jquery-ui-themes/smoothness/data:image/gif;base64,r0lgodlhaqabaiaaaaaaap/yh5baeaaaaalaaaaaabaaeaaaibraa7
The referrer URL.Referrer URL:  /bundles/styles/i_8i3xs-5-sj8p0m2ipixe9wjfd3aeb8fal7n8lsfdw1?v=PPj8P70FMrfbVfOXNO5inLQDZ4q2hRimKmAkdc6umaQ1


Nop logs the same error over and over.
7 年 前
This is caused by jQuery UI.
7 年 前
I have the same issue in 3.80.
6 年 前
Looks like this issue has been occurring for quite some time, and we see it tracks back to the css files.
Does anyone know of a way to stop these errors from cluttering up the error log (and increasing db size) ?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.