-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possibility to set User-Agent #424
Comments
because the value for before running anything, somewhere in code call you can use your custom string there. I can add this to next iteration, no promise on release timeline. you can however use |
Ok, thanks. Will try to patch. I have a stupid question: why don't let set the UserAgent string arbitrarily? |
This is based on original c# code by microsoft |
I uncommented the line where the user agent is added to the header and in my code I added this line:
I got this header:
So I think the setting user agent should be modified as well. PS
then I got:
|
We need to set User-Agent for our project as it's required by customer security policy.
In ExchangeSerivceBase.js there is a line that set User-Agent but it is commented out:
// request.headers["User-Agent"] = this.UserAgent || ExchangeServiceBase.defaultUserAgent; //todo:fix -> Noje.js is refusing to set this unsafe header -//
I tried to uncomment it and it seems working fine. At least I got no errors and I can see that the header is set (using override(https) to hijack requests sent, will try wireahark later).
Would it be possible to restore this feature?
Another question if I set user-agent using
ExchangeService.UserAgent = 'my-user-agent'
it adds ...(ExchangeService/undefined):why?
The text was updated successfully, but these errors were encountered: