#1
|
||||
|
||||
Feature Request: User can define standard User Agent string
I noticed that often the User Agent of JD contains an outdated version of Firefox.
Some webpages don't like that... I would recommend to always use the latest User Agent version of e.g. Firefox. And I would suggest to implement an option (in advanced settings) that the user can enter their own User Agent string. For the time being, only with some Hoster PlugIns the user can define that string. But when I look e.g. at the VK.com PlugIn, default settings read Code:
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0 Or is 46.0 being used for a reason? |
#2
|
||||
|
||||
Quote:
Currently there are no plans for this because there is no need to and custom/different UA can easily break plugins, for example some plugins/api do require a special UA to work properly, and see my comment above.
__________________
JD-Dev & Server-Admin Last edited by Jiaz; 04.06.2022 at 16:00. |
#3
|
||||
|
||||
In case a plugin uses a customized UA, there is a reason. for example different behaviour/layout/js.
Of course it might be outdated and newer UA might work but there is no need to change it when it's working.
__________________
JD-Dev & Server-Admin |
#4
|
||||
|
||||
For example? We're happy to check and update accordingly
__________________
JD-Dev & Server-Admin |
#5
|
||||
|
||||
In fact, VK.com is an example.
With v46.0 you sometimes get unwanted popups, asking you to use another browser or you cannot even access the page at all. Haven't observed this in JD so far, but I did observe this with an outdated Firefox browsers v56.x.x. And it may very well have been the reason for some problems already - without knowing it for sure... Another reason, why I would avoid using the same outdated version for a longer period of time is the following: As you know, many hosters try to detect the use of download managers and then block them. Now, if JD uses e.g. Firefox 46.0 User Agent for a longer period of time, some IT guys at e.g. VK.com may notice that and know, that people are using JD instead of streaming their videos. One should try to avoid them noticing that... An as soon as they notice that, a modification of the corresponding PlugIn is needed... |
#6
|
||||
|
||||
Quote:
as long as the UA does not change the behaviour/flow of the website, all good, which is the case here
__________________
JD-Dev & Server-Admin Last edited by Jiaz; 04.06.2022 at 16:23. |
#7
|
||||
|
||||
Quote:
__________________
JD-Dev & Server-Admin |
#8
|
||||
|
||||
Correct! But in that case we'll notice it (either ourselves or by reports), but if ppl just start changing UA themselves, guess who they gonna ask for help or complain when plugin breaks/fails. The many ping/pongs until ...*ah..sorry..my fault..I did experiment with different UA*.
__________________
JD-Dev & Server-Admin |
#9
|
|||
|
|||
Is there a way to find out the useragent being used at the moment of use by jdownloader by looking at any option or logfile? Without third party software.
In advanced options you can see some plugins able to change from JDDEFAULT to whatever, but what is JDDEFAULT? I'm looking for the user-agent string, not to change it. |
#10
|
||||
|
||||
Quote:
You will find it in the logged http headers. Quote:
It can change and it is not exposed in any of our settings which is why the string "JDDEFAULT" is used in plugin settings in this case. Currently that resembles to: Code:
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:76.0) Gecko/20100101 Firefox/76.0
__________________
JD Supporter, Plugin Dev. & Community Manager
Erste Schritte & Tutorials || JDownloader 2 Setup Download |
14.07.2023, 02:58 |
djones |
Message deleted by pspzockerscene.
Reason: Deleted/edited by user so this comment is/was now useless
|
Thread Tools | |
Display Modes | |
|
|