
Security News
Another Round of TEA Protocol Spam Floods npm, But It’s Not a Worm
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.
Set a custom HTTP status code for the client by utilizing proxy and a meta tag.
Set a custom HTTP status code for the client by utilizing proxy and a meta tag.
Note: Manipulating HTTP status code is not recommended for production. Use at your own risk.
pnpm add set-status
You can configure all settings with the environment variables.
TARGET_URL as your target app URL, http://localhost:3000 by default.PROXY_SERVER_PORT for the proxy server port, 3001 by default.TARGET_META_NAME for the target meta tag, set-status by default.IGNORE_PATH_REGEX for the regex to ignore the target path set to Next.js by default.See
.env.examplefor an example.
Run the proxy server with the following command:
pnpm proxy-status
The proxy server will look for the target meta tag and set the status code to the client.
<meta name="set-status" content="401" />
The meta tag above will let the proxy server set the status code to 401.
Install concurrently to run the proxy server and your production app concurrently.
pnpm add concurrently
Set your start script in package.json as follows:
{
"scripts": {
"start": "concurrently \"pnpm proxy-status\" \"YOUR PRODUCTION COMMAND\""
}
}
pnpm start
See examples in
examples/nextjs.
In Next.js, you can statically set a custom meta tag by using a Metadata API.
Through this, we can set the status code read from the target meta tag.
// page.tsx
export default function Unauthorized() {
return (
<div>
<h1>401</h1>
<p>Unauthorized</p>
</div>
)
}
export const metadata = {
other: {
'set-status': 401,
},
}
Also, you can dynamically set the target meta tag by using generateMetadata function.
// page.tsx
export async function generateMetadata() {
const res = await fetch('https://example.com/api')
if (res.status !== 200) {
return {
other: {
'set-status': res.status,
},
}
}
}
For more information about the Metadata API, see the Next.js documentation.
FAQs
Set a custom HTTP status code for the client by utilizing proxy and a meta tag.
We found that set-status demonstrated a not healthy version release cadence and project activity because the last version was released 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
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.

Security News
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads

Research
/Security News
A malicious Chrome extension posing as an Ethereum wallet steals seed phrases by encoding them into Sui transactions, enabling full wallet takeover.