# Limitations

This project is intentionally a pure HTTP range-semantics library. It provides no:

- HTTP server or HTTP client;
- file I/O or networking;
- full MIME parser or multipart parser;
- cache implementation;
- authorization or access-control system.

If-Range validation (RFC 9110 §13.1.5) covers parsing, strong entity-tag
comparison, and IMF-fixdate normalization. It does not evaluate representations,
track validators across requests, or implement weak comparison semantics.
Entity-tags are restricted to visible ASCII (`etagc` without `obs-text`), and
HTTP-dates are restricted to the canonical 29-character IMF-fixdate shape.

Multiple-range support only plans concrete intervals and per-part metadata. It
does not read a representation, choose a random boundary, encode headers, or
stream a multipart body.

Multipart boundaries must be supplied explicitly by the caller so planning stays
deterministic across all compilation targets.

Unknown range units are parsed as tokens with retained raw data, but their range
sets are not interpreted. Response status values are recommendations after caller
policy, not commands to an HTTP implementation.

Error offsets are MoonBit string code-unit offsets. They are not advertised as
UTF-8 byte offsets.