-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
592 lines (554 loc) · 21.4 KB
/
index.html
File metadata and controls
592 lines (554 loc) · 21.4 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
<!DOCTYPE html>
<html lang="en">
<head>
<title>HTTP Status Codes</title>
<meta charset="UTF-8">
<meta name="description" content="HTTP status codes from 100 to 500">
<meta name="keywords" content="HTML, status code">
<meta name="author" content="Hagge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<style>
/* Neo-Brutalist Style - Because beauty is overrated. */
@import url("https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:ital,wght@0,400;0,700;1,400;1,700&display=swap");
*,
*::before,
*::after {
box-sizing: border-box;
}
::selection {
background: #333;
color: #eee;
}
body {
font-family: "IBM Plex Mono", monospace;
color: #333;
margin: 0;
position: relative;
line-height: 1.5em;
font-size: 15px;
background: #ccc repeating-linear-gradient(45deg,
#aaa,
#aaa 2px,
#ccc 2px,
#ccc 6px);
background-attachment: fixed;
}
.dashboard {
display: grid;
grid-template-columns: repeat(6, 15.25%);
grid-gap: 0 1.67%;
margin: 20px auto;
padding: 20px;
border: 2px solid;
width: 1000px;
max-width: calc(100% - 40px);
background: #ddd;
box-shadow: 1px 1px, 2px 2px, 3px 3px, 4px 4px;
}
.dashboard>div {
margin-bottom: 20px;
padding: 15px;
background-color: #f7f7f7;
border: 2px solid;
grid-column: 1 / 7;
box-shadow: inherit;
}
.dashboard>div:hover {
background: #fff;
color: black;
}
.dashboard>div:last-of-type {
margin-bottom: 5px;
}
.table-wrap {
max-width: 100%;
overflow-x: auto;
}
h2 {
font-size: 1.5em;
line-height: 1.1em;
text-transform: uppercase;
letter-spacing: 0.05em;
margin-top: 0;
padding: 5px 10px;
margin-bottom: 15px;
border-bottom: 2px solid;
position: relative;
}
table {
width: 100%;
border-collapse: collapse;
}
th,
td {
border: 2px solid #333;
padding: 8px;
text-align: left;
}
tr:hover td {
background: #eee;
}
th {
background-color: #666;
color: #fff;
}
ul {
list-style-type: none;
padding: 0;
}
li {
padding: 5px 0;
border-bottom: 2px solid;
}
.profile {
text-align: center;
}
.profile h2 {
font-size: 2em;
padding-bottom: 10px;
border: none;
}
.profile p {
font-size: 1.25em;
font-style: italic;
margin-bottom: 10px;
}
footer {
text-align: center;
padding: 20px;
}
.obsolete {
color: darkgray;
}
</style>
</head>
<body>
<main>
<div class="dashboard">
<div class="profile">
<h1>HTTP Status Codes</h1>
</div>
<div class="schedule-table">
<h2>500-range</h2>
<div class="table-wrap">
<table>
<tr>
<td>500</td>
<td>Internal Server Error</td>
<td>An unexpected error occurred on the server, the request will not be fulfilled. No more specific error was suitable (or maybe the server just doesn not want to specify exactly what went wrong)</td>
</tr>
<tr>
<td>501</td>
<td>Not Implemented</td>
<td>Request method isn't implemented yet.</td>
</tr>
<tr>
<td>502</td>
<td>Bad Gateway</td>
<td>Server acted as a proxy, got an invalid response from upstream server (the next server in the chain).
</td>
</tr>
<tr>
<td>503</td>
<td>Service Unavailable</td>
<td>Server cannot handle the request. Usually because it is temporarily down or overloaded.</td>
</tr>
<tr>
<td>504</td>
<td>Gateway Timeout</td>
<td>Usually happens when your server is acting as a proxy and the other server timed out</td>
</tr>
<tr>
<td>505</td>
<td>HTTP Version Not Supported</td>
<td>HTTP protocol version used in the request is not supported by the server.</td>
</tr>
<tr>
<td>506</td>
<td>Variant Also Negotiates</td>
<td>Circular reference. The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.
</td>
</tr>
<tr>
<td>507</td>
<td>Insufficient Storage</td>
<td>Server is unable to store the representation needed to complete the request.</td>
</tr>
<tr>
<td>508</td>
<td>Loop Detected</td>
<td>Server detected an infinite loop while processing the request (instead of 208 Already Reported)
</td>
</tr>
<tr>
<td>510</td>
<td>Not Extended</td>
<td>The policy for accessing the resource has not been met in the request. Server should send back
all
the
information necessary for the client to issue an extended request.</td>
</tr>
</table>
</div>
</div>
<div class="schedule-table">
<h2>400-range</h2>
<div class="table-wrap">
<table>
<tr>
<td>400</td>
<td>400 Bad Request</td>
<td>Server can't or won't process request. Commonly due to the request having incorrect path or queryparams. Can also happen when the request is too large.</td>
</tr>
<tr>
<td>401</td>
<td>Unauthorized</td>
<td>Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or
has not yet
been provided. Note: Some sites incorrectly issue HTTP 401 when an IP address is banned from the
website
(usually
the website domain) and that specific address is refused permission to access a website.</td>
</tr>
<tr>
<td>402</td>
<td>Payment Required</td>
<td>Reserved for future use. The original intention was that this code might be used as part of some
form of
digital
cash or micropayment but that has not yet happened, and this code is not widely used.</td>
</tr>
<tr>
<td>403</td>
<td>Forbidden</td>
<td>Server refuses to perform requerst. Normally due to missing permissions or a prohibited action (like creating a duplicate)</td>
</tr>
<tr>
<td>404</td>
<td>Not Found</td>
<td>The requested resource could not be found but may be available in the future. Subsequent requests by
the
client
are permissible.</td>
</tr>
<tr>
<td>405</td>
<td>Method Not Allowed</td>
<td>A request method is not supported for the requested resource; for example, a GET request on a form
that
requires
data to be presented via POST, or a PUT request on a read-only resource.</td>
</tr>
<tr>
<td>406</td>
<td>Not Acceptable</td>
<td>Server can't serve response matching request headers. (Example: it serves 'application/json' but request included 'Accept: application/xml')</td>
</tr>
<tr>
<td>407</td>
<td>Proxy Authentication required</td>
<td>The client must first authenticate itself with the proxy.</td>
</tr>
<tr>
<td>408</td>
<td>Request Timeout</td>
<td>Server timed out waiting for the request. Maybe try again at a later time?</td>
</tr>
<tr>
<td>409</td>
<td>Conflict</td>
<td>The request could not be processed because of conflict in the current state of the resource, such as
an
edit
conflict between multiple simultaneous updates</td>
</tr>
<tr>
<td>410</td>
<td>Gone</td>
<td>Resource has been intentionally removed forever</td>
</tr>
<tr>
<td>411</td>
<td>Length Required</td>
<td>The request did not specify the length of its content, which is required by the requested resource.
</td>
</tr>
<tr>
<td>412</td>
<td>Precondition Failed</td>
<td>Server does not meet one of the preconditions that the requester put on the request header
fields.
</td>
</tr>
<tr>
<td>413</td>
<td>Payload Too Large</td>
<td>The request is larger than the server is willing or able to process. Previously called "Request
Entity
Too
Large".</td>
</tr>
<tr>
<td>414</td>
<td>URI Too Long</td>
<td>The URI provided was too long for the server to process. Often the result of too much data being
encoded
as a
query-string of a GET request, in which case it should be converted to a POST request. Called
"Request-URI
Too
Long" previously.</td>
</tr>
<tr>
<td>415</td>
<td>Unsupported Media Type</td>
<td>The request entity has a media type which the server or resource does not support. For example, the
client
uploads an image as image/svg+xml, but the server requires that images use a different format.</td>
</tr>
<tr>
<td>416</td>
<td>Range Not Satisfiable</td>
<td>The client has asked for a portion of the file (byte serving), but the server cannot supply that
portion. For
example, if the client asked for a part of the file that lies beyond the end of the file. Called
"Requested Range
Not Satisfiable" previously.</td>
</tr>
<tr>
<td>417</td>
<td>Expectation Failed</td>
<td>Server cannot meet the requirements of the Expect request-header field.</td>
</tr>
<tr>
<td>418</td>
<td>I'm a teapot</td>
<td>Easter egg from 1998 as one of the traditional IETF April Fools jokes</td>
</tr>
<tr>
<td>421</td>
<td>Misdirected Request</td>
<td>The request was directed at a server that is not able to produce a response (for example because of
connection
reuse).</td>
</tr>
<tr>
<td>422</td>
<td>Unprocessable Entity</td>
<td>The request was well-formed but was unable to be followed due to semantic errors.</td>
</tr>
<tr>
<td>423</td>
<td>Locked</td>
<td>The resource that is being accessed is locked</td>
</tr>
<tr>
<td>424</td>
<td>Failed Dependency</td>
<td>The request failed because it depended on another request and that request failed (e.g., a
PROPPATCH).
</td>
</tr>
<tr>
<td>425</td>
<td>Too Early</td>
<td>Server is unwilling to risk processing a request that might be replayed</td>
</tr>
<tr>
<td>426</td>
<td>Upgrade Required</td>
<td>The client should switch to a different protocol such as TLS/1.3, given in the Upgrade header field.
</td>
</tr>
<tr>
<td>428</td>
<td>Precondition Required</td>
<td>The origin server requires the request to be conditional. Intended to prevent the 'lost update'
problem,
where a
client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third
party
has
modified the state on the server, leading to a conflict.</td>
</tr>
<tr>
<td>429</td>
<td>Too Many Requests</td>
<td>There's rate-limiting and the user has sent too many requests in a given amount of time.</td>
</tr>
<tr>
<td>431</td>
<td>Request Header Fields Too Large</td>
<td>Either an individual header field, OR all
header
fields collectively, are too large - according to this server.</td>
</tr>
<tr>
<td>451</td>
<td>Unavailable For Legal Reasons</td>
<td>A server operator has received a legal demand to deny access to a resource or to a set of resources
that
includes the requested resource.</td>
</tr>
</table>
</div>
</div>
<div class="schedule-table">
<h2>300-range</h2>
<div class="table-wrap">
<table>
<tr>
<td>300</td>
<td>Multiple Choices</td>
<td>Indicates multiple options for the resource from which the client may choose (For example, this
code
could be
used to present multiple video format options).</td>
</tr>
<tr>
<td>301</td>
<td>Moved Permanently</td>
<td>A redirect. Future requests should ideally be directed to the new URL.</td>
</tr>
<tr class="obsolete">
<td>302</td>
<td>"Found" or "Moved temporarily"</td>
<td>This status code still works but it is kinda obsolete since many browsers violated the standard. It's basically a redirect to another URL. Consider using 307 "Temporary Redirect" instead.</td>
</tr>
<tr>
<td>303</td>
<td>See Other</td>
<td>The response to the request can be found under another URI using the GET method. When received in
response to a
POST (or PUT/DELETE), the client should presume that the server has received the data and should
issue a
new GET
request to the given URI.</td>
</tr>
<tr>
<td>304</td>
<td>Not Modified</td>
<td>The resource has not been modified since the version specified by the request headers
If-Modified-Since
or
If-None-Match. In such case, there is no need to retransmit the resource since the client still has
a
previously-downloaded copy.</td>
</tr>
<tr>
<td>305</td>
<td>Use Proxy</td>
<td>The requested resource is available only through a proxy. The address might be provided in the
response, but many HTTP clients (such as FF and IE) do not obey this status code due to security reasons.
</td>
</tr>
<tr>
<td>307</td>
<td>Temporary Redirect</td>
<td>A redirect to a new URL. In the future the client can keep requesting the old URL. But don't keep a 307 on your server for years, consider switching it to a 301 "Moved Permanently".</td>
</tr>
<tr>
<td>308</td>
<td>Permanent Redirect</td>
<td>The request and all future requests should be repeated using another URI. 307 and 308 parallel the
behaviors of
302 and 301, but do not allow the HTTP method to change. So, for example, submitting a form to a
permanently
redirected resource may continue smoothly.</td>
</tr>
</table>
</div>
</div>
<div class="schedule-table">
<h2>200-range</h2>
<div class="table-wrap">
<table>
<tr>
<td>200</td>
<td>OK</td>
<td>Success! You'll get a response.</td>
</tr>
<tr>
<td>201</td>
<td>Created</td>
<td>The request has been fulfilled, resulting in the creation of a new resource.</td>
</tr>
<tr>
<td>202</td>
<td>Accepted</td>
<td>The request has been accepted for processing, but the processing has not been completed.</td>
</tr>
<tr>
<td>203</td>
<td>Non-Authoritative Information</td>
<td>Server is a transforming proxy that received a 200 OK from its origin, but is returning a
modified
version
of the origin's response.</td>
</tr>
<tr>
<td>204</td>
<td>No Content</td>
<td>Server successfully processed the request, and is not returning any content.</td>
</tr>
<tr>
<td>205</td>
<td>Reset Content</td>
<td>Server successfully processed the request, asks that the requester reset its document view,
and is
not
returning any content.</td>
</tr>
<tr>
<td>206</td>
<td>Partial content</td>
<td>Server is delivering only part of the resource (byte serving) due to a range header sent by
the
client. The
range header is used by HTTP clients to enable resuming of interrupted downloads, or split a
download into
multiple simultaneous streams.</td>
</tr>
</table>
</div>
</div>
<div class="schedule-table">
<h2>100-range</h2>
<div class="table-wrap">
<table>
<tr>
<td>100</td>
<td>Continue</td>
<td>Server has received the request headers and the client should proceed to send the request
body. The
purpose
of the 100 status is to allow a client to determine if the origin server is willing to accept the
request
(based
on the request headers) before the client sends the request body.</td>
</tr>
<tr>
<td>102</td>
<td>Processing</td>
<td>A WebDAV request may contain many sub-requests involving file operations, requiring a long time to
complete the
request. This code indicates that the server has received and is processing the request, but no
response
is
available yet. This prevents the client from timing out and assuming the request was lost.</td>
</tr>
<tr>
<td>103</td>
<td>Early Hints</td>
<td>Used to return some response headers before final HTTP message.</td>
</tr>
</table>
</div>
</div>
</div>
</main>
<footer>
ⓒ Hagge
</footer>
</body>
</html>