Search Results for "rfc"

A simple, lightweight JavaScript API for handling cookies which works in all browsers and accepts any character. It is heavily tested, has no dependency, supports ES modules and supports AMD/CommonJS. It is RFC 6265 compliant, has an useful Wiki, and enables custom encoding/decoding. More than 800 bytes gzipped! This project is RFC 6265 compliant. All special characters that are not allowed in the cookie-name or cookie-value are encoded with each one's UTF-8 Hex equivalent using percent-encoding. The only character in cookie-name or cookie-value that is allowed and still encoded is the percent % character, it is escaped in order to interpret percent input as literal. ...

...Simply select a word, right-click, and you'll see a menu option to define the selected word. The definitions are returned in a new window. The extension implements a DICT protocol client, defined in RFC 2229. By default, the extension queries the DICT server on dict.org for definitions, but it can be configured to use other servers. It works on Firefox, SeaMonkey and Thunderbird.

TheGlobalAddressBook (TGAB) is a Firefox extension using ENUM according to IETF RFC 3761 to provide a globally available, extremly scalable and reliable public addressbook directory.

Capture and archive web resources saving them in RFC-2557 (MHTML) compliant format. This library includes a framework for augmenting the capture process and allowing programmatic control, from downloading through saving. A replacement for CDOSYS/CDONT.

This C++ library has been designed as a Chrome SIP stack. Sippet is an open-source SIP User-Agent library, compliant with the IETF RFC 3261 specification. It can be used as a building block for SIP client software for uses such as VoIP, IM, and many other real-time and P2P communication services. The main target was to enable Javascript applications to use UDP, TCP and TLS transports along WebSocket. Existing SIP solutions for the browser are forced to use the WebSockets API to send/receive SIP messages. ...