Skip to content
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

Proxy #132

Open
gligi opened this issue Mar 3, 2022 · 4 comments
Open

Proxy #132

gligi opened this issue Mar 3, 2022 · 4 comments

Comments

@gligi
Copy link

gligi commented Mar 3, 2022

Hi.
Sorry to hijack this git project issue. I am not sure if it is a issue, but does it run as a service (http)? the main problem we had before with the Microsoft service is that corporate proxies are interfering with the script execution. Is it possible to force no proxy or specify the proxy manually with this library?
Tnx
Igor

@JeremyTCD
Copy link
Member

Hey no problem. Yes, communication between the .Net and Node.js processes occurs over HTTP. The library only supports HTTP.

Just to clarify, could you elaborate on

corporate proxies are interfering with the script execution

Was your issue errors like this: An established connection was aborted by the software in your host machine?

@gligi
Copy link
Author

gligi commented Mar 3, 2022

Thank you for the quick answer. We have some .net logic that migrates json files, but on some machines (windows server) we get exception in form of invalid character at the beginning of the string. my assumption is, that the call to node server gets interrupted by the proxy and instead of the json file it tries to parse the message from the proxy server.

Tomorrow I will check this with our IT guys and try to reproduce, because it happens only on few instances. But I have replaced the INodeService with yours and it works like a charm. Thanks on good work.

@gligi
Copy link
Author

gligi commented Mar 18, 2022

Hi again :) Is it in any way possible to execute the nodejs process without starting the HTTP sever? thx

@JeremyTCD
Copy link
Member

Hey! Not with this library unfortunately.

Just a shot in the dark - might switching to HTTPS help? Since TCP proxies cannot read/edit content over HTTPS, the proxies might ignore requests.

If you can provide more details on the proxies I'd be happy to improve this library so it works in situations like yours.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants