"不确定"和"缓存/ XXX" appened到URL [英] "undefined" and "cache/xxx" appened to URLs

查看:396
本文介绍了"不确定"和"缓存/ XXX" appened到URL的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

首先我认为这或多或少是同样的问题<一href=\"http://stackoverflow.com/questions/11017609/undefined-randomly-appended-in-1-of-requested-urls-on-my-website-since-12-jun\">"undefined"自2012年6月12日在在我的网站URL请求的1%随机添加数据,但因为我是一个新用户并不能对这个职位发表评论,它没有解决办法呢,我只能问一个新问题。

First of all I think this is more or less the same problem as "undefined" randomly appended in 1% of requested urls on my website since 12 june 2012 but since I'm a new user and cannot comment on this post and it has no solution yet, I can only ask a new question.

自2012年6月12日14:22 EET(当第一个错误发生的时刻),我们正经历非常奇怪的问题:
请求我们网站的不到1%,有未定义字符串追加到年底或更换URL的一个有效组成部分,引荐是一个完全有效的URL到现场。例如,我们得到的 http://example.com/foo/undefined一个请求与引用者 http://example.com/foo/bar 或请求的 http://example.com/undefined 与引用者 http://example.com/ (主页)。这些URL来自不同的客户端IP地址,不同的互联网服务供应商和浏览器是最常见的浏览器,但IE和Firefox 3.5还发生。它看起来像是被重写URL以无效的东西,保持原来的URL在参照标记。
我们无法重现这个问题。

Since 12 June 2012 14:22 EET (the moment when the first error happened) we are experiencing very weird problems: Less than 1% of the requests to our site have the "undefined" string appended to the end or replacing a valid part of the url and the referrer is a completely valid URL to the site. For example we get a request for http://example.com/foo/undefined with referer http://example.com/foo/bar or request to http://example.com/undefined with referer http://example.com/ (the homepage). These URLs come from diverse client IP addresses, diverse ISPs and the browser is most often Chrome, but happens also with IE and Firefox 3.5. It seems like something is rewriting the URL to something invalid, keeping the original URL in the referrer tag. We can't reproduce this problem.

我们也exeperiencing源文章的评论中提到另一个问题:我们收到的形式 HTTP的URL请求://例子。 COM /缓存/ XXX 其中xxx看起来像32个字符的字符串的MD5(exmple:3d453e96e68cc01ced7920ae77356078或bbc80a4244caf556fdcaa9fb60231af7)。我们没有在我们的任何有效的URL的缓存的字符串。同一XXX字符串可能来自不同的IP地址数天,甚至数周。而所有这些奇怪的请求来自Chrome浏览器。这个问题并没有开始2012-06-12。它发生至少自今年年初,但比第一次更为罕见。我们不能太重现此问题。

We are also exeperiencing another problem mentioned in the comments of the source post: we are receiving URL requests of the form http://example.com/cache/xxx where xxx looks like 32 character MD5 string (exmple: 3d453e96e68cc01ced7920ae77356078 or bbc80a4244caf556fdcaa9fb60231af7). We don't have the "cache" string in any of our valid URLs. One and the same xxx string may come from diverse IPs for several days, even weeks. And all these weird requests come from a Chrome browser. This problem didn't started on 2012-06-12. It happens at least since the beginning of the year but is much more rare than the first one. We can't reproduce this problem too.

我们的网站是在IIS中,客户端在很大程度上基于JavaScript的,我们正在使用的原型框架(jQuery的没有)。

Our web site is on IIS, the client side is heavily Javascript-based and we are using the Prototype framework (not jquery).

推荐答案

在此基础上的帖子,我反向工程ComplitlyChrome外挂程式/恶意软件,并发现这种扩展注入一个自动完成改进功能,在具有输入文本字段与每个站点抛出未定义请求名称或搜索,q和许多其他的ID。

Based on this post, I reverse-engineered the "Complitly" Chrome Plugin/malware, and found that this extension is injecting an "improved autocomplete" feature that was throwing "undefined" requests at every site that has a input text field with NAME or ID of "search", "q" and many others.

我发现也使enable.js文件(的complitly文件中的一个)被检查称为全局变量suggestmeyes_loaded,看它是否已加载(像一个Singleton)。因此,这个变量设置为true,禁用插件。

I found also that the enable.js file (one of complitly files) were checking a global variable called "suggestmeyes_loaded" to see if it's already loaded (like a Singleton). So, setting this variable to true disables the plugin.

TL:DR;

要禁用的恶意软件并停止不确定的要求,与搜索领域在您的网站将此每一页:

To disable the malware and stop "undefined" requests, apply this to every page with a search field on your site:

<script type="text/javascript">
    window.suggestmeyes_loaded = true;
</script>

这也是恶意软件重定向用户到searchcompletion.com网站,有时显示的竞争对手ADS。因此,应该认真对待。

This malware also redirects your users to a "searchcompletion.com" site, sometimes showing competitors ADS. So, it should be taken seriously.

这篇关于&QUOT;不确定&QUOT;和&QUOT;缓存/ XXX&QUOT; appened到URL的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆