
Security News
libxml2 Maintainer Ends Embargoed Vulnerability Reports, Citing Unsustainable Burden
Libxml2’s solo maintainer drops embargoed security fixes, highlighting the burden on unpaid volunteers who keep critical open source software secure.
pac-proxy-agent
Advanced tools
The pac-proxy-agent npm package is a module for Node.js that allows HTTP/HTTPS requests to respect PAC (Proxy Auto-Configuration) files. PAC files are used to determine the appropriate proxy server when making network requests. This package is useful for applications that need to handle network requests in environments with complex proxy configurations.
HTTP/HTTPS request handling with PAC file
This code sample demonstrates how to use the pac-proxy-agent to make an HTTP request that respects a PAC file located at a specified URL. The agent is then used with the HTTP request options to ensure the request follows the proxy rules defined in the PAC file.
const PacProxyAgent = require('pac-proxy-agent');
const url = require('url');
const agent = new PacProxyAgent('http://example.com/proxy.pac');
const opts = url.parse('http://nodejs.org/api/');
opts.agent = agent;
require('http').get(opts, (res) => {
console.log('Got response: ' + res.statusCode);
}).on('error', (e) => {
console.error('Got error: ' + e.message);
});
The proxy-agent package is similar to pac-proxy-agent in that it provides a way to resolve proxy configurations for HTTP/HTTPS requests. However, proxy-agent supports multiple proxy protocols like HTTP, HTTPS, SOCKS, and PAC, making it more versatile for different proxy scenarios.
The http-proxy-agent package is designed to provide an HTTP agent capable of connecting to an HTTP proxy. Unlike pac-proxy-agent, it does not handle PAC files but is specifically tailored for HTTP proxy connections.
Similar to http-proxy-agent, the https-proxy-agent package is focused on providing an HTTPS agent for proxy connections. It is specifically for HTTPS requests and does not support PAC file resolution like pac-proxy-agent.
The socks-proxy-agent package is a SOCKS (Socket Secure) proxy `http.Agent` implementation for HTTP and HTTPS. This package is useful for routing traffic through SOCKS proxy servers, which is a different use case compared to the PAC file support provided by pac-proxy-agent.
http.Agent
implementation for HTTP and HTTPSThis module provides an http.Agent
implementation that retreives the specified
PAC proxy file and uses it to resolve which HTTP, HTTPS, or
SOCKS proxy, or if a direct connection should be used to connect to the
HTTP endpoint.
It is designed to be be used with the built-in http
and https
modules.
import * as http from 'http';
import { PacProxyAgent } from 'pac-proxy-agent';
const agent = new PacProxyAgent('pac+https://cloudup.com/ceGH2yZ0Bjp+');
http.get('http://nodejs.org/api/', { agent }, (res) => {
console.log('"response" event!', res.headers);
res.pipe(process.stdout);
});
FAQs
A PAC file proxy `http.Agent` implementation for HTTP
The npm package pac-proxy-agent receives a total of 10,343,933 weekly downloads. As such, pac-proxy-agent popularity was classified as popular.
We found that pac-proxy-agent demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Libxml2’s solo maintainer drops embargoed security fixes, highlighting the burden on unpaid volunteers who keep critical open source software secure.
Research
Security News
Socket researchers uncover how browser extensions in trusted stores are used to hijack sessions, redirect traffic, and manipulate user behavior.
Research
Security News
An in-depth analysis of credential stealers, crypto drainers, cryptojackers, and clipboard hijackers abusing open source package registries to compromise Web3 development environments.