@aglyn/shared-util-http

中文文档
1.18.0发布于 2026/11/07Apache-2.0TypeScriptES Module构建来源已验证近 30 天下载 1.8万

Small HTTP helpers for Fetch API and Next.js request handlers: CORS, request headers, an ID-token cookie, same-origin redirect checks, URL scheme allowlists, and an authenticated fetch. It is mainly a dependency of the larger Aglyn packages (`@aglyn/agl

原始使用文档
文档目录5 节
  1. Install
  2. What's in it
  3. Usage
  4. How it fits
  5. License

@aglyn/shared-util-http

Small HTTP helpers for Fetch API and Next.js request handlers: CORS, request headers, an ID-token cookie, same-origin redirect checks, URL scheme allowlists, and an authenticated fetch. It is mainly a dependency of the larger Aglyn packages (@aglyn/aglyn, the plugins, the tenant runtime) and is usable on its own.

Published to npm from the Aglyn monorepo. Versions follow semantic versioning.

Install

npm install @aglyn/shared-util-http

Peer dependency: next (16.3.3), optional. You need it when you use the helpers that take Next.js objects (NextRequest, NextResponse, NextApiRequest), such as the cookie helpers. The subpath modules below use only web standards.

What's in it

From the package root:

  • CORS: corsHandleResponse(req, res, options?) and corsBuildResponseHandler(options?), which curries a reusable configuration. Deny-by-default: with no origin option the response is returned untouched. credentials is never paired with a * origin. Preflight OPTIONS requests are answered for you unless preflightContinue is set. Lower-level pieces: getOriginHeaders, getOriginHeadersFromRequest, getAllowedHeaders, isOriginAllowed.
  • getRequestHeader(request, name) - reads a header from either a Fetch Request or a NextApiRequest.
  • getAbsoluteUrl(path, request?) - builds an absolute URL from the host header (server) or window.location (browser).
  • cookieGetUserIdToken(request) / cookieSetUserIdToken(request, response, token, options?) - read and write the user ID-token cookie, httpOnly by default.
  • Types: CorsOptions, StaticOrigin, OriginFn.

By subpath only (not re-exported from the root):

  • @aglyn/shared-util-http/safe-redirect - isSameOriginPath(candidate) and safeSameOriginPath(candidate, fallback = '/'). Instead of pattern-matching the string, they resolve it with the URL parser against a probe origin and accept it only if the origin is unchanged, which catches //host, /\host, and tab or newline tricks alike.
  • @aglyn/shared-util-http/safe-url-scheme - hasSafeLinkScheme(value) (http, https, mailto, tel, sms, or no scheme) and hasSafeMediaScheme(value) (http, https, or no scheme). They check the scheme only; you still have to escape the value into the attribute afterwards.
  • @aglyn/shared-util-http/bounded-await - boundedAwait(work, ms, fallback, label) and createSettledValueCache(). The first answers with work's result, or with fallback once ms has passed, using a real timer rather than trusting an abort signal; work may be a function of an AbortSignal that aborts at the deadline. A deadline that wins writes one structured console.warn per label a minute. The second is a TTL cache that holds settled values and refuses a promise, with a readThrough(key, load, ttlFor) that stores only once load has settled.
  • @aglyn/shared-util-http/authorized-token - resolveIdToken(user, options?), authorizedFetch(user, input, init?, options?), describeCallFailure(error, fallback), AuthorizationUnavailableError, ID_TOKEN_TIMEOUT_MS. user is anything with a getIdToken() method. The token wait has a deadline, and when no token can be had authorizedFetch sends nothing and resolves to a 401-shaped response carrying the reason.

Usage

import { corsBuildResponseHandler } from '@aglyn/shared-util-http'
import { safeSameOriginPath } from '@aglyn/shared-util-http/safe-redirect'

const cors = corsBuildResponseHandler({
  origin: ['https://app.example.com'],
  credentials: true,
})

export async function GET(req: Request) {
  return cors(req, Response.json({ ok: true }))
}

// Anything that would leave the origin becomes '/'.
const next = safeSameOriginPath(new URL(location.href).searchParams.get('next'))

How it fits

A shared package: generic, with no knowledge of Aglyn's model. Shared packages may only import other shared packages; this one depends on @aglyn/shared-data-enums (HTTP status codes and the cookie key). @aglyn/shared-util-next, @aglyn/shared-util-rest-api, @aglyn/shared-util-email, @aglyn/aglyn, the tenant runtime packages and most plugins depend on it.

License

Apache-2.0. Source: https://github.com/aglyn/aglyn/tree/main/libs/shared/util/http

版本与发布记录

@aglyn/shared-util-http 共发布 152 个版本,首次发布于 2026/09/21;过去 12 个月发布了 152 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
1.18.0latest2026/11/07今天
1.17.02026/11/07今天
1.16.02026/11/07今天
1.15.22026/11/061 天前
1.15.12026/11/061 天前
1.15.02026/11/061 天前

其他发布通道:beta → 1.0.0-beta.296。

关于 @aglyn/shared-util-http 的常见问题

@aglyn/shared-util-http 是什么?

Small HTTP helpers for Fetch API and Next.js request handlers: CORS, request headers, an ID-token cookie, same-origin redirect checks, URL scheme allowlists, and an authenticated fetch. It is mainly a dependency of the larger Aglyn packages (`@aglyn/agl

如何安装 @aglyn/shared-util-http?

在项目目录运行 npm install @aglyn/shared-util-http,或使用 pnpm add / yarn add / bun add。

@aglyn/shared-util-http 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@aglyn/shared-util-http 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@aglyn/shared-util-http 可以商用吗?

@aglyn/shared-util-http 使用 Apache-2.0 许可。宽松许可:允许商业使用、修改和再分发,并附带明确的专利授权;分发时需保留许可与 NOTICE 文件,修改过的文件要注明改动。以上为概括,不构成法律意见,请以许可原文为准。

@aglyn/shared-util-http 的下载量有多少?

根据 npm 官方下载统计,@aglyn/shared-util-http 在 2026/10/05 – 2026/11/03 这 30 天内被下载 17,625 次,日均约 588 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@aglyn/shared-util-http 还在维护吗?

最新版本 1.18.0 发布于 2026/11/07(今天);至今共发布 152 个版本,其中过去 12 个月发布了 152 个;首次发布于 2026/09/21。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。