Skip to content

Commit bd84380

Browse files
MalexMalex
Malex
authored and
Malex
committed
Implements shobrook#3, refactor shobrook#6
Not using man interface for this, although probably should
1 parent 635c0ce commit bd84380

File tree

1 file changed

+241
-4
lines changed

1 file changed

+241
-4
lines changed

statcode/header_descriptions.yml

+241-4
Original file line numberDiff line numberDiff line change
@@ -44,10 +44,12 @@ Authorization:
4444
description: "Authentication credentials for HTTP authentication."
4545

4646
Cache-Control:
47-
message: "Cache-Control: no-cache"
48-
category: "Client Request"
49-
description: "Used to specify directives that must be obeyed by all caching mechanisms \
50-
along the request-response chain."
47+
message: "Client= Cache-Control: no-cache
48+
Server= Cache-Control: max-age=3600"
49+
category: "Client Request, Server Response"
50+
description: "For client: Used to specify directives that must be obeyed by all caching mechanisms \
51+
along the request-response chain.
52+
For Server: Tells all caching mechanisms from server to client whether they may cache this object. It is measured in seconds"
5153

5254
Connection:
5355
message: "Connection: keep-alive
@@ -191,3 +193,238 @@ Warning:
191193
category: "Client Request, Server Response"
192194
description: "A general warning about possible problems with the entity body."
193195

196+
Access-Control-Allow-Origin:
197+
message: "Access-Control-Allow-Origin: *"
198+
category: "Server Response"
199+
description: "Specifying which web sites can participate in cross-origin resource sharing"
200+
201+
Access-Control-Allow-Credentials:
202+
message: "Access-Control-Allow-Origin: *"
203+
category: "Server Response"
204+
description: "Specifying which web sites can participate in cross-origin resource sharing"
205+
206+
Access-Control-Expose-Headers:
207+
message: "Access-Control-Allow-Origin: *"
208+
category: "Server Response"
209+
description: "Specifying which web sites can participate in cross-origin resource sharing"
210+
211+
Access-Control-Max-Age:
212+
message: "Access-Control-Allow-Origin: *"
213+
category: "Server Response"
214+
description: "Specifying which web sites can participate in cross-origin resource sharing"
215+
216+
Access-Control-Allow-Methods:
217+
message: "Access-Control-Allow-Origin: *"
218+
category: "Server Response"
219+
description: "Specifying which web sites can participate in cross-origin resource sharing"
220+
221+
Access-Control-Allow-Headers:
222+
message: "Access-Control-Allow-Origin: *"
223+
category: "Server Response"
224+
description: "Specifying which web sites can participate in cross-origin resource sharing"
225+
226+
Accept-Patch:
227+
message: "Accept-Patch: text/example;charset=utf-8"
228+
category: "Server Response"
229+
description: "Specifies which patch document formats this server supports."
230+
231+
Accept-Ranges:
232+
message: "Accept-Ranges: bytes"
233+
category: "Server Response"
234+
description: "What partial content range types this server supports via byte serving."
235+
236+
Age:
237+
message: "Age: 12"
238+
category: "Server Response"
239+
description: "The age the object has been in a proxy cache in seconds."
240+
241+
Allow:
242+
message: "Allow: GET, HEAD"
243+
category: "Server Response"
244+
description: "Valid methods for a specified resource. To be used for a 405 Method not allowed."
245+
246+
Alt-Svc:
247+
message: "Alt-Svc: http/1.1=\"http2.example.com:8001\"; ma=7200"
248+
category: "Server Response"
249+
description: "A server uses \"Alt-Svc\" header (meaning Alternative Services) to indicate that its resources can also \
250+
be accessed at a different network location (host or port) or using a different protocol.
251+
When using HTTP/2, servers should instead send an ALTSVC frame."
252+
253+
Content-Disposition:
254+
message: "Content-Disposition: attachment; filename=\"fname.ext\""
255+
category: "Server Response"
256+
description: "An opportunity to raise a \"File Download\" dialogue box for a known MIME type with binary format \
257+
or suggest a filename for dynamic content. Quotes are necessary with special characters."
258+
259+
Content-Language:
260+
message: "Content-Language: it"
261+
category: "Server Response"
262+
description: "The natural language or languages of the intended audience for the enclosed content"
263+
264+
Content-Location:
265+
message: "Content-Location: /index.htm"
266+
category: "Server Response"
267+
description: "An alternate location for the returned data."
268+
269+
Content-Range:
270+
message: "Content-Range: bytes 21010-47021/47022"
271+
category: "Server Response"
272+
description: "Where in a full body message this partial message belongs."
273+
274+
Delta-Base:
275+
message: "Delta-Base: \"abc\""
276+
category: "Server Response"
277+
description: "Specifies the delta-encoding entity tag of the response."
278+
279+
ETag:
280+
message: "ETag: \"737060cd8c284d8af7ad3082f209582d\""
281+
category: "Server Response"
282+
description: "An identifier for a specific version of a resource, often a message digest."
283+
284+
Expires:
285+
message: "Expires: Thu, 01 Dec 1994 16:00:00 GMT"
286+
category: "Server Response"
287+
description: "Gives the date/time after which the response is considered stale (in \"HTTP-date\" format as defined by RFC 7231)."
288+
289+
IM:
290+
message: "IM: feed"
291+
category: "Server Response"
292+
description: "Instance-manipulations applied to the response."
293+
294+
Last-Modified:
295+
message: "Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT"
296+
category: "Server Response"
297+
description: "The last modified date for the requested object (in \"HTTP-date\" format as defined by RFC 7231)."
298+
299+
Link:
300+
message: "Link: </feed>; rel=\"alternate\""
301+
category: "Server Response"
302+
description: "Used to express a typed relationship with another resource, where the relation type is defined by RFC 5988."
303+
304+
Location:
305+
message: "Location: /pub/WWW/People.html"
306+
category: "Server Response"
307+
description: "Used in redirection, or when a new resource has been created. Can be absolute or relative path \
308+
(if absolute, http:// protocol must be specified)."
309+
310+
P3P:
311+
message: "P3P: CP=\"This is not a P3P policy! See https://en.wikipedia.org/wiki/Special:CentralAutoLogin/P3P for more info.\""
312+
category: "Server Response"
313+
description: "This field is supposed to set P3P policy, in the form of P3P:CP=\"your_compact_policy\".
314+
However, P3P did not take off,[45] most browsers have never fully implemented it, a lot of websites set this field \
315+
with fake policy text, that was enough to fool browsers the existence of P3P policy and grant permissions for third party cookies."
316+
317+
Proxy-Authenticate:
318+
message: "Proxy-Authenticate: Basic"
319+
category: "Server Response"
320+
description: "Request authentication to access the proxy."
321+
322+
Public-Key-Pins:
323+
message: "Public-Key-Pins: max-age=2592000; pin-sha256=\"E9CZ9INDbd+2eRQozYqqbQ2yXLVKB9+xcprMF+44U1g=\";"
324+
category: "Server Response"
325+
description: "HTTP Public Key Pinning, announces hash of website's authentic TLS certificate."
326+
327+
Retry-After:
328+
message: "Retry-After: 120; Retry-After: Fri, 07 Nov 2014 23:59:59 GMT"
329+
category: "Server Response"
330+
description: "If an entity is temporarily unavailable, this instructs the client to try again later. Value could be a specified period of time (in seconds) or a HTTP-date."
331+
332+
Server:
333+
message: "Server: Apache/2.4.1 (Unix)"
334+
category: "Server Response"
335+
description: "A name for the server.
336+
\ Usually provides information about the OS and HTTP Server implementation used, mirroring User Agent"
337+
338+
Set-Cookie:
339+
message: "Set-Cookie: UserID=JohnDoe; Max-Age=3600; Version=1"
340+
category: "Server Response"
341+
description: "Sets an HTTP Cookie on the client."
342+
343+
Strict-Transport-Security:
344+
message: "Strict-Transport-Security: max-age=16070400; includeSubDomains"
345+
category: "Server Response"
346+
description: "A HSTS Policy informing the HTTP client how long to cache the HTTPS only policy and whether this applies to subdomains."
347+
348+
Trailer:
349+
message: "Trailer: Max-Forwards"
350+
category: "Server Response"
351+
description: "The Trailer general field value indicates that the given set of header fields is present in the trailer of a message encoded with chunked transfer coding."
352+
353+
Transfer-Encoding:
354+
message: "Transfer-Encoding: chunked"
355+
category: "Server Response"
356+
description: "The form of encoding used to safely transfer the entity to the user. Currently defined methods are:\
357+
chunked, compress, deflate, gzip, identity.
358+
Must not be used with HTTP/2."
359+
360+
Tk:
361+
message: "Tk: ?"
362+
category: "Server Response"
363+
description: "Tracking Status header, value suggested to be sent in response to a DNT(do-not-track), possible values:
364+
\"!\" — under construction
365+
\"?\" — dynamic
366+
\"G\" — gateway to multiple parties
367+
\"N\" — not tracking
368+
\"T\" — tracking
369+
\"C\" — tracking with consent
370+
\"P\" — tracking only if consented
371+
\"D\" — disregarding DNT
372+
\"U\" — updated."
373+
374+
Vary:
375+
message: "Vary: * ; Vary: Accept-Language"
376+
category: "Server Response"
377+
description: "Tells downstream proxies how to match future request headers to decide whether the cached response can be used rather than requesting a fresh one from the origin server."
378+
379+
WWW-Authenticate:
380+
message: "WWW-Authenticate: Basic"
381+
category: "Server Response"
382+
description: "Indicates the authentication scheme that should be used to access the requested entity."
383+
384+
X-Frame-Options:
385+
message: "X-Frame-Options: deny"
386+
category: "Server Response"
387+
description: "Clickjacking protection: deny - no rendering within a frame, sameorigin - no rendering if origin mismatch, allow-from - allow from specified location, allowall - non-standard, allow from any location."
388+
389+
Refresh:
390+
message: "Refresh: 5; url=http://www.example.com/pub/statcode/fun_times.html"
391+
category: "Server Response"
392+
description: "Used in redirection, or when a new resource has been created. This refresh redirects after 5 seconds. Header extension introduced by Netscape and supported by most web browsers. NOT STANDARD."
393+
394+
Status:
395+
message: "Status: 200 OK"
396+
category: "Server Response"
397+
description: "CGI header field specifying the status of the HTTP response. Normal HTTP responses use a separate \"Status-Line\" instead, defined by RFC 7230. NOT STANDARD."
398+
399+
X-XSS-Protection:
400+
message: "X-XSS-Protection: 1; mode=block"
401+
category: "Server Response"
402+
description: "Cross-site scripting (XSS) filter. NOT STANDARD."
403+
404+
X-UA-Compatible:
405+
message: "X-UA-Compatible: IE=EmulateIE7 ; X-UA-Compatible: IE=edge ; X-UA-Compatible: Chrome=1"
406+
category: "Server Response"
407+
description: "Recommends the preferred rendering engine (often a backward-compatibility mode) to use to display the content. Also used to activate Chrome Frame in Internet Explorer. NOT STANDARD."
408+
409+
X-Powered-By:
410+
message: "X-Powered-By: PHP/5.4.0"
411+
category: "Server Response"
412+
description: "Specifies the technology (e.g. ASP.NET, PHP, JBoss) supporting the web application (version details are often in X-Runtime, X-Version, or X-AspNet-Version). NOT STANDARD."
413+
414+
X-Content-Type-Options:
415+
message: "X-Content-Type-Options: nosniff"
416+
category: "Server Response"
417+
description: "The only defined value, \"nosniff\", prevents Internet Explorer from MIME-sniffing a response away from the declared content-type. This also applies to Google Chrome, when downloading extensions. NOT STANDARD."
418+
419+
X-Requested-With:
420+
message: "X-Requested-With: XMLHttpRequest"
421+
category: "Client Request"
422+
description: "Mainly used to identify Ajax requests. Most JavaScript frameworks send this field with value of XMLHttpRequest. NOT STANDARD."
423+
424+
DNT:
425+
message: "DNT: 1 (Do Not Track Enabled) ; DNT: 0 (Do Not Track Disabled)"
426+
category: "Client Request"
427+
description: "Requests a web application to disable their tracking of a user.
428+
This is Mozilla's version of the X-Do-Not-Track header field (since Firefox 4.0 Beta 11). \
429+
Safari and IE9 also have support for this field.
430+
On March 7, 2011, a draft proposal was submitted to IETF. The W3C Tracking Protection Working Group is producing a specification."

0 commit comments

Comments
 (0)