npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@betaathe/node-red-contrib-http-ntlm-req

v0.2.1

Published

HTTP request with NTLM

Downloads

7

Readme

node-red-contrib-http-ntlm-req

Node-red nodes that allow users to send HTTP request with NTLM auth.

Forked from: https://github.com/IdanZel/node-red-contrib-http-ntlm-req

Modifications

  • Added PUT support
  • Added compatibility with msg.params, to allow to add parameters to the end of the URL in all three methods.
  • Solved some minor bugs
  • Removed unused config params
  • Added msg.url to change the URL of the node
  • Content-type is now set on POST and PUT to application/json if not set. You can overwrite it at any moment with msg.headers["Content-Type"]
  • Now only 4XX and 5XX status codes are marked as an error.

Usage

To set up HTTP request, create a new auth config:

  • Enter the URL address to the URL field.
  • Fill in the Username, Password and Domain if needed.

Then, set up the node:

  • Set a name
  • Optionally, set a URL. If not set, you must define msg.url with the URL.
  • Select GET, POST or PUT method

Finally, you can add some msg variables:

  • msg.url: Overwrites the URL of the node.
  • msg.params: In all methods, it's going to be concatenated to the end of url (for example, given a url https://example.com and msg.params="?param1=1&param2=2", the final URL is going to be https://example.com?param1=1&param2=2). You don't need to set up msg.params if you are already using msg.url and viceversa, as the two values are simply concatenated. The only requirement is to have set the URL value in the config of the node, the msg.url or the msg.params.
  • msg.headers: Dictionary of the headers to be sent. If you are sending any value via POST or PUT methods and you don't set the Content-type, it's going to be set up automatically for you as application/json.
  • msg.payload: The body of the message in POST and PUT methods. It's stringified automatically, so your payload can be an object or a string.

The body of the response is going to be set at msg.payload as a string. You need to parse it, if needed, later.