Home

1xx

In the context of HTTP, the 1xx class of status codes represents informational responses. They indicate that a request has been received and that the client should continue with the request or prepare for further action. 1xx responses are provisional and do not convey a final result about the request.

Common examples of 1xx status codes include:

- 100 Continue: The server has received the request headers and the client can continue sending the

- 101 Switching Protocols: The server is changing to a different protocol as requested by the client,

- 102 Processing: Used by certain servers (notably WebDAV) to indicate that the request has been accepted

- 103 Early Hints: The server can send preliminary headers to speed up the rendering of a page

Characteristics and usage:

1xx responses are interim and are not meant to be cached in standard practice. They usually do

Standards and evolution:

The 1xx class is defined within the HTTP/1.1 specification and has been described in successive RFCs, including

See also: HTTP status codes.

request
body.
If
the
request
body
is
large,
this
can
help
avoid
sending
it
unnecessarily.
typically
via
the
Upgrade
header
(for
example,
to
WebSocket).
for
processing
but
is
not
yet
complete.
by
suggesting
resources
to
preload
before
the
final
response
is
ready.
not
contain
a
message
body,
with
some
exceptions
like
103
that
may
include
header
fields.
The
final
outcome
of
the
request
is
conveyed
by
the
ultimate
status
code
in
the
2xx,
3xx,
4xx,
or
5xx
ranges.
RFC
2616
and
later
updates
in
RFC
7230
through
RFC
7235.
The
103
Early
Hints
code
was
specified
in
RFC
8297
to
enable
preloading
of
resources
during
page
load.