Additional HTTP Status Codes

Nottingham, Mark; Fielding, Roy T.

doi:10.17487/rfc6585

Cited by 16 publications

(16 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A server that receives a larger header block than it is willing to handle can send an HTTP 431 (Request Header Fields Too Large) status code [RFC6585]. A client can discard responses that it cannot process.…”

Section: Limits On Header Block Sizementioning

confidence: 99%

Hypertext Transfer Protocol Version 2 (HTTP/2)

Belshe¹,

Thomson²,

Peon³

2015

390

241

View full text Add to dashboard Cite

This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2). HTTP/2 enables a more efficient use of network resources and a reduced perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection. It also introduces unsolicited push of representations from servers to clients.

show abstract

Section: Limits On Header Block Sizementioning

confidence: 99%

Hypertext Transfer Protocol Version 2 (HTTP/2)

Belshe¹,

Thomson²,

Peon³

2015

390

241

View full text Add to dashboard Cite

show abstract

“…A push service MAY return a 429 (Too Many Requests) status code [RFC6585] to reject requests that omit a subscription set.…”

Section: Collecting Subscriptions Into Setsmentioning

confidence: 99%

“…If a push service wishes to limit the number of receipt subscriptions that it maintains, it MAY return a 429 (Too Many Requests) status code [RFC6585] to reject receipt requests that omit a receipt subscription.…”

Section: Requesting Push Message Deliverymentioning

confidence: 99%

“…A push service MAY return a 429 (Too Many Requests) status code [RFC6585] when an application server has exceeded its rate limit for push message delivery to a push resource. The push service SHOULD also include a Retry-After header [RFC7231] to indicate how long the application server is requested to wait before it makes another request to the push resource.…”

Section: Denial-of-service Considerationsmentioning

confidence: 99%

See 1 more Smart Citation

Generic Event Delivery Using HTTP Push

Damaggio¹,

Thomson²,

Raymor³

2016

View full text Add to dashboard Cite

show abstract

“…The GW function is responsible for filtering traffic to the Internet so that only authenticated clients gain access. The latter is achieved using a captive portal that answers DNS requests on behalf of the mobile nodes and/or terminates and redirects HTTP connections targeted to a node on the Internet to a local HTTPS authentication server, using 30x or 511 [11] HTTP response codes. The authentication server then prompts the user to enter her credentials.…”

Section: Commercial Wlan Hot-spotsmentioning

confidence: 99%

Enabling ad-hoc-style communication in public WLAN hot-spots

Kärkkäinen

Pitkänen

Ott

2012

Proceedings of the Seventh ACM International Workshop on Challenged Networks

View full text Add to dashboard Cite

Opportunistic networking between mobile devices relies on the capabilities of those devices to establish ad-hoc communication among each other. While the two dominant wireless interface technologies, IEEE 802.11 wireless LAN and Bluetooth, offer such capabilities in theory, limitations of the protocol specification, chipsets, and operating systems in mobile devices render those features largely unusable in practice. Researchers have recognized these shortcomings and devised mechanisms in which mobile devices act as WLAN access points to simulate WLAN infrastructure-based operation. In this paper, we complement these approaches by instrumenting commercial WLAN APs that do not employ L2 security to serve as link layer packet relays without requiring the mobile nodes to authenticate with the WLAN hot-spot. We present different mechanisms for peer discovery, evaluate their feasibility for a set of commercial hot-spots, and discuss operational considerations for fair use of commercial access points.

show abstract

Additional HTTP Status Codes

Cited by 16 publications

References 5 publications

Hypertext Transfer Protocol Version 2 (HTTP/2)

Hypertext Transfer Protocol Version 2 (HTTP/2)

Generic Event Delivery Using HTTP Push

Enabling ad-hoc-style communication in public WLAN hot-spots

Contact Info

Product

Resources

About