ttys3

 changes: 1. the host name logic changed to be consistent with the GUI one (just like the `QString getHost(const QString &url)`) 2. fixed: just like the GUI, the tracker...

@thalieht and, I have to say, during the fixup, I found the the GUI version has a bug dealing with hostname. in `QString getHost(const QString &url)` (https://github.com/qbittorrent/qBittorrent/blob/ecc08dee0969b69330ca32b762df1a847ca2cb89/src/gui/transferlistfilters/trackersfilterwidget.cpp#L76) it simply do...

> @ttys3 > > Any way to test this changes using a docker image? If not possible I will wait for the release, thanks for all your work currently no...

the CI complains about the style. I ran `npm run format` and pushed the change PTAL

@brvphoenix thank you for the detailed review I will push the changes late in this week, mostly in the weekend.

right click context menu has been added according @brvphoenix 's suggestion: 

@brvphoenix as long as it is good for the project, I am OK with that. you can make another PR.

LGTM one NIT: my bad, the var name should refined: `urls` => `messages` in ```js new ClipboardJS('.copyLogDataToClipboard', { text: function() { let urls = []; currentTable.selectedRowsIds().each(function(rowId) { urls.push(currentTable.rows.get(rowId).full_data[(currentSelectedTab === "main")...

as discussed https://github.com/qbittorrent/qBittorrent/pull/18189#issuecomment-1359452845 a new PR will replace this one, see : https://github.com/qbittorrent/qBittorrent/pull/18290

I also ran into this problem today. The client may initiate different content-types, and I need to decide whether to make a streaming response or a simple json response based...