搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

How to stop constant retry of blocked post requests

more options

I have ublock origin add-on installed and it is filtering certain posts requests on citi.com. (I also asked my question with ublock origin but thought I would see if there's a more general solution within Firefox itself) Anyway, these blocked post requests are constantly being retried, causing a barrage of error messages in the Console and Network developer tools. The error message in the console is "blocked by uBlock Origin" and the error messages in the Network are:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://contents1.00110.citi.com/api/v1/sendLogs?cid=cedric&cdsnum=X-sjnF-Y-Z-W-B-C&csid=D&ds=js&sdkVer=A. (Reason: CORS request did not succeed). Status code: (null).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://contents2.00110.citi.com/client/v3.1/web/wup?cid=cedric. (Reason: CORS request did not succeed). Status code: (null).

over and over again. Even without the devtools open, this activity is using 20% of my CPU.

Wondering how I can stop this constant retrying of post requests? Thanks

I have ublock origin add-on installed and it is filtering certain posts requests on citi.com. (I also asked my question with ublock origin but thought I would see if there's a more general solution within Firefox itself) Anyway, these blocked post requests are constantly being retried, causing a barrage of error messages in the Console and Network developer tools. The error message in the console is "blocked by uBlock Origin" and the error messages in the Network are: ''Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://contents1.00110.citi.com/api/v1/sendLogs?cid=cedric&cdsnum=X-sjnF-Y-Z-W-B-C&csid=D&ds=js&sdkVer=A. (Reason: CORS request did not succeed). Status code: (null). Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://contents2.00110.citi.com/client/v3.1/web/wup?cid=cedric. (Reason: CORS request did not succeed). Status code: (null).'' over and over again. Even without the devtools open, this activity is using 20% of my CPU. Wondering how I can stop this constant retrying of post requests? Thanks

所有回复 (7)

more options

If it was just to retrieve information, the page probably would display an error message. Maybe it's some kind of analytics script that keeps reporting on (or trying to report on) what you are doing in the page?

Does the page still repeat the POST if you unblock it?

more options

jscher2000 - Support Volunteer said

If it was just to retrieve information, the page probably would display an error message. Maybe it's some kind of analytics script that keeps reporting on (or trying to report on) what you are doing in the page? Does the page still repeat the POST if you unblock it?

It's constantly retrying the post connections even if i don't have the tab active. If I unblock it then it stops repeating.

more options

I guess you could ask the bank WTF is going on with that script. It sounds like it's performing a very uncool denial of service on you if you don't allow the connection.

I don't know whether there is a way to halt the script without a really deep dive into how it is set up.

more options

Dropa said

Addon blocker issue isn't something firefox forum user help with that is up to the developer to address their Addon issues.

It is not against the rules to ask for help with using an Extension here. Yes the Extension author may have their own support forum or a thread on the independent mozillaZine forums or such. Not all Extension devs are going to be able to do one on one support though.

more options

Ye and I thought there might be some global or internal option for Firefox to help stop such a DoS attack.

Either way, I got a preliminary solution from uBO people and I still had to modify it so it wasn't logging each block to the Developer Console, that was the main/only cause of the high CPU use.

more options

The Extension reviews on A.M.O is not for support purposes.

You keep posting that their only option to get help with anything to do with insert Extension is to contact the extension author.

more options

After further testing, seems to be something more going on than just uBlockOrigin blocking a bunch of post requests. I tried using a blank/new FF profile and something is still triggering high CPU usages ~30% on my computer, when normally it is 5-8% after the page is done loading. If I switch to another tab, then CPU drops somewhat to ~20% but is still too high. Does this Profiler help figure out what the problem is? https://share.firefox.dev/3CrLYPM