Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
fimiproxy
Advanced tools
Readme
simple HTTP | HTTPS reverse proxy in node.js. currently supports:
host
header to pre-configured origin server. see https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Hosthttp | https
request to origin http | https
servernpm i fimiproxy -g
npm i fimiproxy
npm i fimiproxy -D
replace npm
with yarn
or any other package manager of choice.
{
"exposeHttpProxy": false,
"exposeHttpsProxy": false,
"httpPort": "",
"httpsPort": "",
"httpsPublicKeyFilepath": "",
"httpsPrivateKeyFilepath": "",
"httpsPublicKey": "",
"httpsPrivateKey": "",
"routes": [
{
"originHost": "",
"originPort": "",
"originProtocol": "http:",
"incomingHostAndPort": ""
}
]
}
exposeHttpProxy
— set to true
to expose an HTTP server, requires httpPort
to be set if true
exposeHttpsProxy
— set to true
to expose an HTTPS server, requires httpsPort
, httpsPublicKey
OR httpsPublicKeyFilepath
, httpsPrivateKey
OR httpsPrivateKeyFilepath
to be set if true
httpPort
— port HTTP server should listen on, when exposeHttpProxy
is true
httpsPort
— port HTTPS server should listen on, when exposeHttpsProxy
is true
httpsPublicKeyFilepath
— filepath to TLS certificate (public key) used with HTTPS serverhttpsPrivateKeyFilepath
— filepath to TLS private key used with HTTPS serverhttpsPublicKey
— TLS certificate (public key) string used with HTTPS server. takes precedence over httpsPublicKeyFilepath
httpsPrivateKey
— TLS private key string used with HTTPS server. takes precedence over httpsPrivateKeyFilepath
routes
— array of incoming host to origin protocol, host, and port
originHost
— origin host or IPoriginPort
— origin portoriginProtocol
— origin protocol. one of http:
or https:
. don't forget the :
at the endincomingHostAndPort
— incoming host:port
to proxy to origin server. picked from HTTP host
header fieldfimiproxy ./path/to/config.json
npm exec fimiproxy ./path/to/config.json
npx -y fimiproxy ./path/to/config.json
import fimiproxy from "fimiproxy"
// start fimiproxy
await fimiproxy.startFimiproxyUsingConfig({
/** config */ {
exposeHttpProxy: false,
exposeHttpsProxy: false,
httpPort: "80",
httpsPort: "443",
routes: [{
originHost: "localhost",
originPort: "6001",
originProtocol: "https:",
incomingHostAndPort: "www.fimidara.com:80",
}],
httpsPublicKey: "",
httpsPrivateKey: "",
httpsPublicKeyFilepath: "",
httpsPrivateKeyFilepath: "",
},
/** shouldHandleGracefulShutdown */ true,
/** exitProcessOnShutdown */ true,
});
// end fimiproxy
await fimiproxy.endFimiproxy(/** exitProcessOnShutdown */ true);
startFimiproxyUsingConfig
— start fimiproxy using config
config: FimiproxyRuntimeConfig
— see configuration aboveshouldHandleGracefulShutdown
— defaults to true
. if true
, will listen for SIGINT
and SIGTERM
, and attempt to gracefully shut down the proxy serverexitProcessOnShutdown
— defaults to true
. if shouldHandleGracefulShutdown
is true
, will call process.exit()
after graceful shutdown. your process may not shut down after SIGINT
and SIGTERM
if not true
. currently untested behaviour (if process will shutdown or not) when set to false
and shouldHandleGracefulShutdown
is true
startFimiproxyUsingConfigFile
— start fimiproxy using config read from filepath
filepath: string
— file at filepath should be a json file, see configuration section abovestartFimiproxyUsingProcessArgs
— start fimiproxy using filepath picked from process.argv[2]
see https://nodejs.org/docs/latest/api/process.html#processargv. example, node your-script.js ./path/to/config.json
endFimiproxy
— gracefully end fimiproxy
exitProcess
— defaults to true
. calls process.exit()
if true
endFimiproxy
before making another start call. start calls are calls to startFimiproxyUsingConfig
, startFimiproxyUsingConfigFile
, or startFimiproxyUsingProcessArgs
FAQs
simple HTTP and HTTPS reverse proxy
The npm package fimiproxy receives a total of 0 weekly downloads. As such, fimiproxy popularity was classified as not popular.
We found that fimiproxy 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
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.