You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2074,7 +2074,7 @@ Please note, everything said above will happen only if you set `useEntityNames:
2074
2074
## Using Proxy
2075
2075
2076
2076
**Node.js Only.** Starting from v.1.7.2 DynamicsWebApi supports different types of connections through proxy. To make it possible, I added two dependencies in a `package.json`:
2077
-
(http-proxy-agent)[https://github.com/TooTallNate/node-https-proxy-agent] and (https-proxy-agent)[https://github.com/TooTallNate/node-http-proxy-agent], based on a type of a protocol, DynamicsWebApi
2077
+
[http-proxy-agent](https://github.com/TooTallNate/node-https-proxy-agent) and [https-proxy-agent](https://github.com/TooTallNate/node-http-proxy-agent), based on a type of a protocol, DynamicsWebApi
2078
2078
will use one of those agents.
2079
2079
2080
2080
In order to let DynamicsWebApi know that you are using proxy you have two options:
@@ -2083,16 +2083,16 @@ In order to let DynamicsWebApi know that you are using proxy you have two option
0 commit comments