套件：node-auth-header（1.0.0~1.1.0+~2.0.1~ds+~6.1.0+~0~20180821-1）
node-auth-header 的相關連結
Debian 的資源：
下載原始碼套件 jsbundle-web-interfaces：
- [jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~6.1.0+~0~20180821-1.dsc]
- [jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~6.1.0+~0~20180821.orig-Xauth.tar.gz]
- [jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~6.1.0+~0~20180821.orig-Xhttp.tar.gz]
- [jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~6.1.0+~0~20180821.orig-Xwebidl.tar.gz]
- [jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~6.1.0+~0~20180821.orig.tar.gz]
- [jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~6.1.0+~0~20180821-1.debian.tar.xz]
維護小組：
相似套件：
parse HTTP auth/authz headers - Node.js library
auth-header deals with obscene HTTP "Authorization" and "WWW-Authenticate" headers.
The HTTP "Authorization" and "WWW-Authenticate" family of headers are both pretty nightmareish; there has been, up until recently, no wide consensus about how they should be formatted and so parsing them is lots of fun if fun is pulling your hair out.
This library provides an implementation of RFC7235 which allows for the parsing of many known existing authorization headers (like Basic and Digest) as well as any future ones which follow the standard. Noteably, this library is less strict than it could be to parse some of these legacy formats.
In addition to the format of the header itself being in flux, WWW-Authenticate has its own nasty surprise: sometimes multiple authentication prompts can appear in one header, sometimes they can appear in multiple headers; we _ONLY_ support the latter case since trying to disambiguate between a second prompt and parameters for the first is just about impossible.
This package provides auth-header usable with Node.js - an event-based server-side JavaScript engine.
其他與 node-auth-header 有關的套件
|
|
|
|
-
- dep: nodejs
- evented I/O for V8 javascript - runtime executable