admin管理员组文章数量:1323342
I'm gettig some strange HTTP requests, like:
"POST /type_error:SafeUrl HTTP/1.1"
"GET /some/path/type_error:SafeUrl HTTP/1.1"
"POST /another/long/path/type_error:SafeUrl HTTP/1.1"
"POST /another/very/long/path/type_error:SafeUrl HTTP/1.1"
Mainly POST
but GET
too, mainly on iPhone, and I'm quite sure that the origin is triggered by some "type_error" in JS.
The only pattern is /type_error:SafeUrl at the end of the URL.
Unfortunately I'm not able to reproduce it.
As I can see it es from Fundingchoices library.
How can I solve/dig/approach this issue?
I know that this is not a fully pliant query, but I hope to match the same "bad" experience in someone that had already solved this problem.
I'm gettig some strange HTTP requests, like:
"POST /type_error:SafeUrl HTTP/1.1"
"GET /some/path/type_error:SafeUrl HTTP/1.1"
"POST /another/long/path/type_error:SafeUrl HTTP/1.1"
"POST /another/very/long/path/type_error:SafeUrl HTTP/1.1"
Mainly POST
but GET
too, mainly on iPhone, and I'm quite sure that the origin is triggered by some "type_error" in JS.
The only pattern is /type_error:SafeUrl at the end of the URL.
Unfortunately I'm not able to reproduce it.
As I can see it es from Fundingchoices library.
How can I solve/dig/approach this issue?
I know that this is not a fully pliant query, but I hope to match the same "bad" experience in someone that had already solved this problem.
Share Improve this question edited Jan 25, 2022 at 7:20 Ivan Buttinoni asked Jan 21, 2022 at 9:43 Ivan ButtinoniIvan Buttinoni 4,1451 gold badge27 silver badges45 bronze badges4 Answers
Reset to default 8I think it is a bug in Funding Choices.
Deep down in some ad-blocking detection code loaded by Funding Choices I found the following being part of a reportClientEvent(...) call:
_.Cc = function(a) {
return a instanceof _.Vb && a.constructor === _.Vb ? a.g : "type_error:SafeUrl"
}
a.g
is a URL (https://fundingchoicesmessages.google./el/AGSKWxVK...
) but a
is not an instance of _.Vb
, so we end up with type_error:SafeUrl
being returned as the URL for the XMLHttpRequest request.
I expect this to be a bug because requesting 'type_error:SafeUrl' without domain or protocol will not result in anything useful.
These kinds of requests started yesterday (2022-01-20 17:30 UTC) in large amounts on our website, suggesting that an update was release around that time somewhere. I wish I could find a changelog for Funding Choices ...
UPDATE: I've been in touch with the Funding Choice team, and they expect to release a fix early next week (possible Monday).
UPDATE: Malformed traffic disappeared on our server at around 2022-01-25 23:00 UTC.
None of these requests pass the Cloudflare JS Challenge.enter image description here
been getting this too on my sites, tons of it.
seeing the answer here, the only thing i can think of is a few days ago i activated GDPR and CCPA in adsense.
perhaps report to adsense feedback?
After applying different solutions I found out the real cause. And that is the script of Google Adsense.
Our web server was not able to handle the type_error:SafeUrl and it was choking the RAM of our server. so once we removed the adsbygoogle.js file website was restored and worked fine. I don't know why Google release this update without testing.
本文标签: javascriptstrange HTTP request ending with quottypeerrorSafeUrlquotStack Overflow
版权声明:本文标题:javascript - strange HTTP request ending with "type_error:SafeUrl" - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1742134574a2422312.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论