#1
|
|||
|
|||
User-Agent in Event Scripter
I have an event set up where JD2 grabs some information from my website. My site generates the output based on the client so it would be pretty handy if JD2 would send an actual meaningful User-Agent instead of the default Firefox one.
|
#2
|
||||
|
||||
You can customize Headers via setHeader method. For example setHeader("User-Agent","Test")
That should work as expected
__________________
JD-Dev & Server-Admin |
#3
|
|||
|
|||
Thanks for the tip, I must've missed that when looking for it myself.
Although I do think that my issue is still valid: It doesn't matter if I identify JD2 with a GET parameter, or custom header or whatever; JD2 should identify itself from the get-go. This just puts the burden on the user. |
#4
|
||||
|
||||
I'm sorry but that Browser instance within your scripts is the same as in plugins.
If you need special handling/identification on server side via UA/Header/Get Parameter, then it's customization. Plugins rely on server responses to be the same as in browser, so we use a normal UA for that.
__________________
JD-Dev & Server-Admin Last edited by Jiaz; 27.11.2020 at 17:47. |
Thread Tools | |
Display Modes | |
|
|