Well, all items in the sample file work for me in 20.05 and I cannot see why they should fail.
Also, my own ~250 items that I am monitoring are also working just fine.
Can you simply try again? Maybe at a different time/day and/or with a different ISP / computer?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tested it more and it only happens when using WebChangeMonitor_22_05-32bit-Win7.zip on Windows 7 x86. On my Windows 11 based PE (x64), all 4 32bit and 64 bit releases of WCM v22.05 for Windows work fine.
Can you test it using WebChangeMonitor_22_05-32bit-Win7.zip on Windows 7 x86?
My Sandy Bridge MSI laptop, which only supports Windows 7, has not broken yet, so I have to keep using it.
Last edit: circcc 2022-05-15
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If it is a bug: Chances are very good that with the next release of cURL this is fixed and therefore also fixed in WCM.
You can also provide me with an example and I report to the cURL guys. For that purpose I would leave this ticket open for a while. But as there is nothing I can do (and I definitely won't stick to an old cURL version for the sake of security) I'll close this ticket sooner or later.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So, what I did (and it will be available in the next release): Such issues may arise if the server does a more strict checking. Unfortunately you can't have a "one fits all implementation" here: Either you setup to be strict and it may fail on certain web pages or you relax the checking and it will fail on others. The default behaviour of WCM is to be "relaxed", meaning no strict checking and that should fit to 95+% of all pages. Obviously not for this one. Therefore, with the new release I have implemented an access layer to setup the fundamental behaviour of libCURL. If you set this up to your needs it should work. But be warned: It may fail with others then... Thats the nature of the internet since we have providers like cloudfare, unfortunately...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
WCM v22.06 still not working in win7.
I've tried changing the connectivity settings around, but 269 out of 569 items are still broken. So, it seems that the minimum OS requirement for WCM is now Windows 10.
I will continue to use the WCM v22.03 version for win7. WCM v22.04 works too but it has a translation bug which is fixed in WCM v22.06.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the report. Did you really use curl with the same version for testing (from above)? because the underlying lib is binary the same and this should work...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
...you could do me a favour:
If you run curl.exe like this:
curl --libcurl client.c https://example.com
...then it will write a C-file (client.c). Please post this here. Before, exchange example.com with a page that works using the command line tool but does not work sing WCM.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
FYI, WebChangeMonitor_22_05-32bit-Win7.zip
Sample WebChangeMonitor.config is attached.
Last edit: circcc 2022-05-15
Well, all items in the sample file work for me in 20.05 and I cannot see why they should fail.
Also, my own ~250 items that I am monitoring are also working just fine.
Can you simply try again? Maybe at a different time/day and/or with a different ISP / computer?
I tested it more and it only happens when using WebChangeMonitor_22_05-32bit-Win7.zip on Windows 7 x86. On my Windows 11 based PE (x64), all 4 32bit and 64 bit releases of WCM v22.05 for Windows work fine.
Can you test it using WebChangeMonitor_22_05-32bit-Win7.zip on Windows 7 x86?
My Sandy Bridge MSI laptop, which only supports Windows 7, has not broken yet, so I have to keep using it.
Last edit: circcc 2022-05-15
Well I don't have access to a Win7-x86 box, unfortunately. So it seems a very special thing. I would suggest the following:
1.) Try to find an example that is broken in the command-line curl tool. To do do, download the current binary release from here:
https://curl.se/windows/dl-7.83.1_1/curl-7.83.1_1-win32-mingw.zip
...and an old one from here:
https://curl.se/windows/dl-7.82.0/curl-7.82.0-win32-mingw.zip
2.) Report with steps-to-reproduce to the cURL guys here:
https://lists.haxx.se/listinfo/curl-users
...and ask whether this is a bug or they don't support Window 7-x86 anymore.
If it is a bug: Chances are very good that with the next release of cURL this is fixed and therefore also fixed in WCM.
You can also provide me with an example and I report to the cURL guys. For that purpose I would leave this ticket open for a while. But as there is nothing I can do (and I definitely won't stick to an old cURL version for the sake of security) I'll close this ticket sooner or later.
"curl-7.83.1_1-win32-mingw.zip" have no error in my win7 x86.
Broken URLs in WCM v22.05 are loaded normally in CURL.
Could you please post the exact command line you've used for cURL that works on Win7-x86?
curl https://www.xnview.com/en/xnview/
So, what I did (and it will be available in the next release): Such issues may arise if the server does a more strict checking. Unfortunately you can't have a "one fits all implementation" here: Either you setup to be strict and it may fail on certain web pages or you relax the checking and it will fail on others. The default behaviour of WCM is to be "relaxed", meaning no strict checking and that should fit to 95+% of all pages. Obviously not for this one. Therefore, with the new release I have implemented an access layer to setup the fundamental behaviour of libCURL. If you set this up to your needs it should work. But be warned: It may fail with others then... Thats the nature of the internet since we have providers like cloudfare, unfortunately...
WCM v22.06 still not working in win7.
I've tried changing the connectivity settings around, but 269 out of 569 items are still broken. So, it seems that the minimum OS requirement for WCM is now Windows 10.
I will continue to use the WCM v22.03 version for win7. WCM v22.04 works too but it has a translation bug which is fixed in WCM v22.06.
Thanks for the report. Did you really use curl with the same version for testing (from above)? because the underlying lib is binary the same and this should work...
...you could do me a favour:
If you run curl.exe like this:
curl --libcurl client.c https://example.com
...then it will write a C-file (client.c). Please post this here. Before, exchange example.com with a page that works using the command line tool but does not work sing WCM.
Here is client.c file.
BTW, as this FR is closed, please track:
https://sourceforge.net/p/webchangemon/feature-requests/227/
...for further updates.
There will be news soon...