| Discussion Forum: Thread 289940 |
|
 |
| | | Author: | Kenopolis  | | Posted: | May 18, 2021 12:36 | | Subject: | Inventory pages won't load | | Viewed: | 67 times | | Topic: | Help | |
|
| I've been getting warning messages from avast antivirus,
and now my inventory won't load.
(see picture.)
It appears that the warning is not needed, but if the page is being blocked that
could be a problem.
I see you are getting ready to shut the site down for a bit... Perhaps this is
one of the issues to be corrected? (Futile hoping)
Thanks to MrPetovan for his help, he said:
Thank you for the details, at least now we know the URL Avast is mad about.
It's this one: https://static.bricklink.com/renovate/js/build/cookieNotice.build.js
TL;DR: You're fine, you can disregard this particular alert.
At a glance it looks like a regular minified Javascript library file. The only
suspect thing is that it provides a base64 encoded data: URL as a SourceMap which
is used to debug the library even when it is minified.
This is probably what tripped Avast as base64 encoded data is routinely used
in malware to conceal a harmful payload, but I don't think it was warranted
in this case.
|
|
|
|
| | | | | |
| | | | | Author: | Pippysblocks | | Posted: | May 18, 2021 14:47 | | Subject: | Re: Inventory pages won't load | | Viewed: | 93 times | | Topic: | Help | |
|
| I've added the following as an exemption
https://static.bricklink.com/*
in Avast go to menu / settings / exceptions and add exception.
Hopefully, this will work.
In Help, Kenopolis writes:
| | I've been getting warning messages from avast antivirus,
and now my inventory won't load.
(see picture.)
It appears that the warning is not needed, but if the page is being blocked that
could be a problem.
I see you are getting ready to shut the site down for a bit... Perhaps this is
one of the issues to be corrected? (Futile hoping)
Thanks to MrPetovan for his help, he said:
Thank you for the details, at least now we know the URL Avast is mad about.
It's this one: https://static.bricklink.com/renovate/js/build/cookieNotice.build.js
TL;DR: You're fine, you can disregard this particular alert.
At a glance it looks like a regular minified Javascript library file. The only
suspect thing is that it provides a base64 encoded data: URL as a SourceMap which
is used to debug the library even when it is minified.
This is probably what tripped Avast as base64 encoded data is routinely used
in malware to conceal a harmful payload, but I don't think it was warranted
in this case.
|
|
|
|
| | | | | | | | | |
| | | | | | | Author: | Kenopolis | | Posted: | May 18, 2021 18:58 | | Subject: | Re: Inventory pages won't load | | Viewed: | 36 times | | Topic: | Help | |
|
| That seems to work.
Thanks.
As someone said in my other post... (this was just about the inventory not working,
the other was about the avast warning)
Makes me wonder how many people (especially new users) won't want to use
this site to buy if they get this notice.
In Help, Pippysblocks writes:
| | I've added the following as an exemption
https://static.bricklink.com/*
in Avast go to menu / settings / exceptions and add exception.
Hopefully, this will work.
In Help, Kenopolis writes:
| | I've been getting warning messages from avast antivirus,
and now my inventory won't load.
(see picture.)
It appears that the warning is not needed, but if the page is being blocked that
could be a problem.
I see you are getting ready to shut the site down for a bit... Perhaps this is
one of the issues to be corrected? (Futile hoping)
Thanks to MrPetovan for his help, he said:
Thank you for the details, at least now we know the URL Avast is mad about.
It's this one: https://static.bricklink.com/renovate/js/build/cookieNotice.build.js
TL;DR: You're fine, you can disregard this particular alert.
At a glance it looks like a regular minified Javascript library file. The only
suspect thing is that it provides a base64 encoded data: URL as a SourceMap which
is used to debug the library even when it is minified.
This is probably what tripped Avast as base64 encoded data is routinely used
in malware to conceal a harmful payload, but I don't think it was warranted
in this case.
|
|
|
|
|
|
|
|
|
USA, Missouri
United Kingdom, England