Hi Team ,
first of all , thanks for bringing such solution to people .
I've been using Webcopy and noticed , although webcopy is able to download the images from site , it still not able to remap CSS inline background-image to the downloaded file , once I navigate offline version copy of site , I am see CSS is referring to blank link where actually webcopy managed to download file .
Any solution ? or is that a bug ?
Thanks ,
[attachment id=0 msg=905]
[attachment id=1 msg=905]
Hello,
Thanks for reporting this issue. It should be remapping CSS so I'm not quite what's up. I had a brief look at the sample you provided (and thank you for taking the time to provide this!) but don't see anything obvious from a cursor glance at the CSS. I'll do some debugging and let you know what I find.
Regards;
Richard Moss
Thanks Richard ,
Appreciated , Wget , httrack and some others have the problem not able to recognize and download images inline css image links but Cyotek webcopy is able to download however not able to remap later on ..
just for the sake of clarity , background-image: url('images/slides/background.jpg'); ...webcopy is able to download background.jpg however in local version of html is still referring to url((unknown));
Regards
Hello,
I've just spent some time scanning the sample you provided and have the following observations:
Assuming the URL to copy was
demo/blog, then I had to change the following settings
- Advanced - Crawl above root URL
- Additional Hosts - Add assets.moredemo.com
Without the "Crawl above root" setting, WebCopy will skip
demo/posts etc. And, as the CSS file was located on
assets.moredemo.com it wouldn't get copied at all without the additional host being set. By default WebCopy will copy
resources from external hosts, but that is things like images or audio files - not CSS.
However, there's also a nice bug I discovered - "above root" handling is broken as it is only comparing the path of the URI, even if is is a different domain. So when copying
demo/blog, it looks at
assets.moredemo.com/css/demo.css and even though it is a completely different domain, decides it is "above the root" and thus skips it.
So that's a bit of an oops - but thank you very much for helping to find this bug. This is from an ancient part of the code base and didn't have any tests - a fact I've just rectified.
I've committed a couple of fixes and normally I would say that a nightly build would be available today except that as part of my (automated) build process each final setup is submitted to VirusTotal and isn't made publicly available unless it comes back clean. And right now SecureAge APEX seems to be taking a perverse delight is flagging all our files as "malicious". I'm 100% this is a false positive, but at the same time I'm not relaxing the process to upload files just because one AV out of 69 has a problem. I have contracted SecureAge with today's build in an effort to find out the problem.
Regards;
Richard Moss
Hi Richard ,
Thanks for sharing insight and observations you had in such quick manner, truly appreciated.
Should we understand with this chance you'll able to apply' correct css mapping ' in the nightly builds ?
css mapping that I refer in the previous post :
background-image: url('images/slides/background.jpg'); ...webcopy is able to download background.jpg however in local version of html is still referring to url((unknown));
Regards
Hello,
I received an automated email from SecureAge this morning stating my false positive samples had been processed, but it would take up to 72 hours for the changes to take affect. I've just tried rescanning build 610 and SecureAge is still flagging it so I'll have to wait a bit longer and hope it clears up. Once they are flagged clean the upload process will automatically start making them available as nightly builds again.
Regards;
Richard Moss
Hi Richard ,
I almost feel I am chasing for nightly build ... ( I think I do !! )
is there any chance we can see the build today and download ?
Regards,
SecureAge responded last Friday saying they'd investigated my files, were happy they were false positives and were no longer flagging the files as suspicious. "Your false detection(s) will be cleared within the next 72 hours" they said. They were pretty much correct - it took until Sunday instruction VirusTotal to rescan the file for it to come up clean.
Unfortunately they have only solved whatever the issue is for one file. Every new build I publish, for any product, is automatically flagged by them as malicious. My VirusTotal submission log is a long list of red at the moment. I logged a support ticket regarding the whole series of files yesterday but I've yet to hear back from them. I'm starting to get to the point where I'm going to blacklist them and if their AV flags my files, I'm going to ignore it. I trust the fact that 60 or so other engines don't have a problem rather than the one that does.
If I don't hear back by tomorrow I'll push build 608 (the one I submitted to SecureAge and which is now flagged as clean) ahead of the others so that it becomes available.
---
I just logged into VirusTotal to check the current status and build 611 is now flagged as clean as well (it was rescanned 5 hours ago). Interesting. All the other files are still flagged by SecureAge but this one is clean. As I said, I haven't heard back from them yet so I don't know if they are fixing the problem but it's clean.
And just as I type this reply, it's 19:00 so the nightly upload tool has just woken up and made build 611 available for download.
I hope this fixes your problem, please let me know if not.
Regards;
Richard Moss
Edit: I've manually rescanned all uploaded builds and SecureAge is no longer flagging them all. Phew. Back in business!
Hi Richard ,
You nailed BIG time ;)
Hope you are aware WEBCOPY is the only freeware product in the web that able to read / copy background-image tags in CSS and able to map correctly , I am saying this because I've been experimenting most of other products which we dont need to name at all anymore !
I can't thank enough ... just for to be at the safe side , I will copy this build in couple of places ;D
Regards,
Thanks for the update glad it's all working correctly!