![]() Later I noticed that these inline styles were added to all the image elements: display: none !important įinally, I did not receive any "failed to load resource" messages in the console, but rather this: Port error: Could not establish connection. The redirect request headers were all for this identical short line of base64-encoded data, and each returned no response, although the status was "Successful": GET data:image/png base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAACklEQVR4nGMAAQAABQABDQottAAAAABJRU5ErkJggg= HTTP/1.1 ![]() Later down the line, there was a second request that listed the original URL and then "Redirect" as the Initiator. The first request would return no response (Status "(pending)"). I was using Chrome's network tab to debug and finding very confusing results for these specific images that failed to load. This wasn't a cross-domain issue for me, and it failed on both localhost and on the web. ![]() ![]() My image URL was /images/ads/homepage/small-banners01.png,Īnd this was tripping up AdBlock. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |