Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Online API
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Jonathan Cardoso via curl-library <curl-library_at_cool.haxx.se>
Date: Sat, 05 Dec 2020 12:50:35 -0300
Try fetching ‘matchmaker.krunker.io [http://matchmaker.krunker.io]’ in curl (like curl match...). It returns the correct response: This server manages matchmaking requests. Now go to node-libcurl and do the equivalent for that module. You get a 403 forbidden error. This is what I mean. There are some differences that I do not know of, and I think that an online api would really help.
node-libcurl author here, feel free to open an issue in the repository (https://github.com/JCMais/node-libcurl) if you are having any issues with the library, please also provide a sample code that can reproduce the issue.
With that said, there is no special proxy handling being done by the Node.js bindings, everything is passed forward as-is to libcurl.
What might be happening in your case is that in the shell you are running `curl` you have the http_proxy environment variable set, but in the one you are running node it's not set. libcurl uses this environment variable internally to set the default values for the proxy option. You can always set the PROXY option yourself if you want to.
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2020-12-05
Date: Sat, 05 Dec 2020 12:50:35 -0300
Try fetching ‘matchmaker.krunker.io [http://matchmaker.krunker.io]’ in curl (like curl match...). It returns the correct response: This server manages matchmaking requests. Now go to node-libcurl and do the equivalent for that module. You get a 403 forbidden error. This is what I mean. There are some differences that I do not know of, and I think that an online api would really help.
node-libcurl author here, feel free to open an issue in the repository (https://github.com/JCMais/node-libcurl) if you are having any issues with the library, please also provide a sample code that can reproduce the issue.
With that said, there is no special proxy handling being done by the Node.js bindings, everything is passed forward as-is to libcurl.
What might be happening in your case is that in the shell you are running `curl` you have the http_proxy environment variable set, but in the one you are running node it's not set. libcurl uses this environment variable internally to set the default values for the proxy option. You can always set the PROXY option yourself if you want to.
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2020-12-05