Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Static file and directory handlers plugin for hapi.js.
Lead Maintainer - Gil Pedersen
inert provides new handler
methods for serving static files and directories, as well as decorating the reply
interface with a file
method for serving file based resources.
last-modified
and etag
headers.content-encoding: gzip
responses.content-disposition
header.inert enables a number of common use cases for serving static assets.
The following creates a basic static file server that can be used to serve html content from the
public
directory on port 3000:
const Path = require('path');
const Hapi = require('hapi');
const Inert = require('inert');
const server = new Hapi.Server({
port: 3000,
routes: {
files: {
relativeTo: Path.join(__dirname, 'public')
}
}
});
const provision = async () => {
await server.register(Inert);
server.route({
method: 'GET',
path: '/{param*}',
handler: {
directory: {
path: '.',
redirectToSlash: true,
index: true,
}
}
});
await server.start();
console.log('Server running at:', server.info.uri);
};
provision();
You can serve specific files using the file
handler:
server.route({
method: 'GET',
path: '/{path*}',
handler: {
file: 'page.html'
}
});
If you need more control, the reply.file()
method is available to use inside handlers:
server.route({
method: 'GET',
path: '/file',
handler(request, reply) {
let path = 'plain.txt';
if (request.headers['x-magic'] === 'sekret') {
path = 'awesome.png';
}
return reply.file(path).vary('x-magic');
}
});
server.ext('onPostHandler', (request, reply) => {
const response = request.response;
if (response.isBoom &&
response.output.statusCode === 404) {
return reply.file('404.html').code(404);
}
return reply.continue;
});
After registration, this plugin adds a new method to the reply
object and exposes the 'file'
and 'directory'
route handlers.
inert accepts the following registration options:
etagsCacheMaxSize
- sets the maximum number of file etag hash values stored in the
etags cache. Defaults to 10000
.Note that inert uses the custom 'file'
variety
to signal that the response is a static
file generated by this plugin.
reply.file(path, [options])
Transmits a file from the file system. The 'Content-Type' header defaults to the matching mime type based on filename extension.:
path
- the file path.options
- optional settings:
confine
- serve file relative to this directory and returns 403 Forbidden
if the
path
resolves outside the confine
directory.
Defaults to true
which uses the relativeTo
route option as the confine
.
Set to false
to disable this security feature.filename
- an optional filename to specify if sending a 'Content-Disposition' header,
defaults to the basename of path
mode
- specifies whether to include the 'Content-Disposition' header with the response.
Available values:
false
- header is not included. This is the default value.'attachment'
'inline'
lookupCompressed
- if true
, looks for for a pre-compressed version of the file with
the same filename with an extension, depending on the accepted encoding.
Defaults to false
.lookupMap
- an object
which maps content encoding to expected file name extension.
Defaults to { gzip: '.gz' }
.etagMethod
- specifies the method used to calculate the ETag
header response.
Available values:
'hash'
- SHA1 sum of the file contents, suitable for distributed deployments.
Default value.'simple'
- Hex encoded size and modification date, suitable when files are stored
on a single server.false
- Disable ETag computation.start
- offset in file to reading from, defaults to 0.end
- offset in file to stop reading from. If not set, will read to end of file.Returns a standard response object.
The response flow control rules do not apply.
file
handlerGenerates a static file endpoint for serving a single file. file
can be set to:
files
configuration).function(request)
which returns the relative or absolute
file path.path
- a path string or function as described above (required).confine
- serve file relative to this directory and returns 403 Forbidden
if the
path
resolves outside the confine
directory.
Defaults to true
which uses the relativeTo
route option as the confine
.
Set to false
to disable this security feature.filename
- an optional filename to specify if sending a 'Content-Disposition'
header, defaults to the basename of path
mode
- specifies whether to include the 'Content-Disposition' header with the
response. Available values:
false
- header is not included. This is the default value.'attachment'
'inline'
lookupCompressed
- if true
, looks for for a pre-compressed version of the file with
the same filename with an extension, depending on the accepted encoding.
Defaults to false
.lookupMap
- an object
which maps content encoding to expected file name extension.
Defaults to { gzip: '.gz' }
.etagMethod
- specifies the method used to calculate the ETag
header response.
Available values:
'hash'
- SHA1 sum of the file contents, suitable for distributed deployments.
Default value.'simple'
- Hex encoded size and modification date, suitable when files are stored
on a single server.false
- Disable ETag computation.start
- offset in file to reading from, defaults to 0.end
- offset in file to stop reading from. If not set, will read to end of file.directory
handlerGenerates a directory endpoint for serving static content from a directory.
Routes using the directory handler must include a path parameter at the end of the path
string (e.g. /path/to/somewhere/{param}
where the parameter name does not matter). The
path parameter can use any of the parameter options (e.g. {param}
for one level files
only, {param?}
for one level files or the directory root, {param*}
for any level, or
{param*3}
for a specific level). If additional path parameters are present, they are
ignored for the purpose of selecting the file system resource. The directory handler is an
object with the following options:
path
- (required) the directory root path (relative paths are resolved based on the
route files
configuration). Value can be:
function(request)
which returns the path string or
an array of path strings. If the function returns an error, the error is passed back
to the client in the response.index
- optional boolean|string|string[], determines if an index file will be served
if found in the folder when requesting a directory. The given string or strings specify
the name(s) of the index file to look for. If true
, looks for 'index.html'. Any falsy
value disables index file lookup. Defaults to true
.listing
- optional boolean, determines if directory listing is generated when a
directory is requested without an index document.
Defaults to false
.showHidden
- optional boolean, determines if hidden files will be shown and served.
Defaults to false
.redirectToSlash
- optional boolean, determines if requests for a directory without a
trailing slash are redirected to the same path with the missing slash. Useful for
ensuring relative links inside the response are resolved correctly. Disabled when the
server config router.stripTrailingSlash
is true.
Defaults to false
.lookupCompressed
- optional boolean, instructs the file processor to look for the same
filename with an extension, depending on the accepted encoding, for a pre-compressed
version of the file to serve. Defaults to false
.lookupMap
- an object
which maps content encoding to expected file name extension.
Defaults to { gzip: '.gz' }
.etagMethod
- specifies the method used to calculate the ETag
header response.
Available values:
'hash'
- SHA1 sum of the file contents, suitable for distributed deployments.
Default value.'simple'
- Hex encoded size and modification date, suitable when files are stored
on a single server.false
- Disable ETag computation.defaultExtension
- optional string, appended to file requests if the requested file is
not found. Defaults to no extension.FAQs
Static file and directory handlers plugin for hapi.js
The npm package inert receives a total of 14,528 weekly downloads. As such, inert popularity was classified as popular.
We found that inert demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers 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.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.