64bit Web File Browser?

[sirksel]

Are there any 64bit successors to HTTP SmartBrowser? I want to browse just like a web browser would and copy certain files, for example on a site like archive.org/download or something like that. I want to use the same interface as is possible with FTP sites. I guess that's what HTTP SmartBrowser does, but I run the 64bit version of TC. Any suggestions?

[Horst.Epp]

What about this one
WFX HTTPS Browser 1.1
https://totalcmd.net/plugring/https_browser.html

[petermad]

https://totalcmd.net/plugring/https_browser.html crashes TC 11.02

This HTTP Browser 1.2.1 plugin works though: https://totalcmd.net/plugring/http2.html

[Fla$her]

This HTTP Browser 1.2.1 plugin works though: https://totalcmd.net/plugring/http2.html

---------------------------
HTTP Plugin Init Error
---------------------------
EIcsLibeayException
Failed to load OpenSSL file ..\Plugins\wfx\HTTPBrowser\x86_ssl_dll\libcrypto-1_1.dll
---------------------------
ОК
---------------------------

[petermad]

2Fla$her
Works fine here under Windows 7 (32-and 64bit plugin) - but I get the same error as you under Windows XP.

https://totalcmd.net/plugring/https_browser.html does not have 32bit wfx

Then there is https://tcmd.madsenworld.dk/plugins/hbrowser_1.1.zip but it is only for http:// not for https://

[Fla$her]

2petermad
That’s the way it is.

[beb]

https://totalcmd.net/plugring/https_browser.html does not have 32bit wfx

It does have 32bit wlx:

"Binary package of the existing plugin without any modifications (both 32-bit and 64-bit versions)"

https://github.com/rg-software/wfx-https-browser/releases/tag/1.1
https://github.com/rg-software/wfx-https-browser/releases/download/1.1/httpsbrowser.zip

[Horst.Epp]

This HTTP Browser 1.2.1 plugin works though: https://totalcmd.net/plugring/http2.html

---------------------------
HTTP Plugin Init Error
---------------------------
EIcsLibeayException
Failed to load OpenSSL file ..\Plugins\wfx\HTTPBrowser\x86_ssl_dll\libcrypto-1_1.dll
---------------------------
ОК
---------------------------

You don't have the right version installed.
The file name of it is here:
PLUGINS\HTTPBrowser\x86_ssl_dll\libcrypto-3.dll

[petermad]

2Horst.Epp

You don't have the right version installed.
The file name of it is here:
PLUGINS\HTTPBrowser\x86_ssl_dll\libcrypto-3.dll

That is the version I have and it works on Windows 7 but not on Windows XP - https://tcmd.madsenworld.dk/httpbrowser121.png

There are references to both the libcrypto-1_1.dll and the libcrypto-3.dll library inside the .wfx file: https://tcmd.madsenworld.dk/httpbrowser121-2.png

[beb]

That is the version I have and it works on Windows 7 but not on Windows XP

Still, you can keep them both at the same time if needed, e.g.

Code: Select all

httpBrowser=%commander_path%\plugins\wfx\httpBrowser\httpbrowser.wfx
httpBrowserXP=%commander_path%\plugins\wfx\httpBrowserXP\httpbrowser.wfx
httpsBrowser=%commander_path%\plugins\wfx\httpsBrowser\httpsbrowser.wfx

Where httpBrowserXP would go with the outdated DLLs for the outdated OS.

[petermad]

2beb

The problem that non of the avaialbale versions works for https under Windows XP, it is only the old http version that works.

[Fla$her]

The file name of it is here:
PLUGINS\HTTPBrowser\x86_ssl_dll\libcrypto-3.dll

To what petermad said, I will add that the location of the wfx plugin folder in PLUGINS instead of PLUGINS\wfx isn't canonical.

[Horst.Epp]

The file name of it is here:
PLUGINS\HTTPBrowser\x86_ssl_dll\libcrypto-3.dll

To what petermad said, I will add that the location of the wfx plugin folder in PLUGINS instead of PLUGINS\wfx isn't canonical.

For me, using the Plugman tool, there is no benefit to have sub-dirs like wfx or wlx under plugins

[beb]

...nstead of PLUGINS\wfx isn't canonical.

Luckily, there are no "canonical" structures for the plugins.
On the contrary, plugins like (wfx)hbrowser_1.2.1 that force keeping mandatory subfolders alike "x64(x86)_ssl_dll" for the required libraries, being unable a) to utilize existing TotalCommander libraries and b) to provide a user an option to choose the libraries, paths, sources, etc they prefer -- are the badly written plugins.

...using the Plugman tool, there is no benefit...

Actually, it's not a big deal for a user to do the same with or without the Plugman tool.

[Fla$her]

Luckily, there are no "canonical" structures for the plugins.

We are talking about what TC offers by default, namely the canonical location, which is specified in various help and ReadMe files.