summaryrefslogtreecommitdiffstats
path: root/index.xml
blob: 0adf185a8c6102dd50450c7d37af56c284f7be3b (plain) (blame)
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
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5052
5053
5054
5055
5056
5057
5058
5059
5060
5061
5062
5063
5064
5065
5066
5067
5068
5069
5070
5071
5072
5073
5074
5075
5076
5077
5078
5079
5080
5081
5082
5083
5084
5085
5086
5087
5088
5089
5090
5091
5092
5093
5094
5095
5096
5097
5098
5099
5100
5101
5102
5103
5104
5105
5106
5107
5108
5109
5110
5111
5112
5113
5114
5115
5116
5117
5118
5119
5120
5121
5122
5123
5124
5125
5126
5127
5128
5129
5130
5131
5132
5133
5134
5135
5136
5137
5138
5139
5140
5141
5142
5143
5144
5145
5146
5147
5148
5149
5150
5151
5152
5153
5154
5155
5156
5157
5158
5159
5160
5161
5162
5163
5164
5165
5166
5167
5168
5169
5170
5171
5172
5173
5174
5175
5176
5177
5178
5179
5180
5181
5182
5183
5184
5185
5186
5187
5188
5189
5190
5191
5192
5193
5194
5195
5196
5197
5198
5199
5200
5201
5202
5203
5204
5205
5206
5207
5208
5209
5210
5211
5212
5213
5214
5215
5216
5217
5218
5219
5220
5221
5222
5223
5224
5225
5226
5227
5228
5229
5230
5231
5232
5233
5234
5235
5236
5237
5238
5239
5240
5241
5242
5243
5244
5245
5246
5247
5248
5249
5250
5251
5252
5253
5254
5255
5256
5257
5258
5259
5260
5261
5262
5263
5264
5265
5266
5267
5268
5269
5270
5271
5272
5273
5274
5275
5276
5277
5278
5279
5280
5281
5282
5283
5284
5285
5286
5287
5288
5289
5290
5291
5292
5293
5294
5295
5296
5297
5298
5299
5300
5301
5302
5303
5304
5305
5306
5307
5308
5309
5310
5311
5312
5313
5314
5315
5316
5317
5318
5319
5320
5321
5322
5323
5324
5325
5326
5327
5328
5329
5330
5331
5332
5333
5334
5335
5336
5337
5338
5339
5340
5341
5342
5343
5344
5345
5346
5347
5348
5349
5350
5351
5352
5353
5354
5355
5356
5357
5358
5359
5360
5361
5362
5363
5364
5365
5366
5367
5368
5369
5370
5371
5372
5373
5374
5375
5376
5377
5378
5379
5380
5381
5382
5383
5384
5385
5386
5387
5388
5389
5390
5391
5392
5393
5394
5395
5396
5397
5398
5399
5400
5401
5402
5403
5404
5405
5406
5407
5408
5409
5410
5411
5412
5413
5414
5415
5416
5417
5418
5419
5420
5421
5422
5423
5424
5425
5426
5427
5428
5429
5430
5431
5432
5433
5434
5435
5436
5437
5438
5439
5440
5441
5442
5443
5444
5445
5446
5447
5448
5449
5450
5451
5452
5453
5454
5455
5456
5457
5458
5459
5460
5461
5462
5463
5464
5465
5466
5467
5468
5469
5470
5471
5472
5473
5474
5475
5476
5477
5478
5479
5480
5481
5482
5483
5484
5485
5486
5487
5488
5489
5490
5491
5492
5493
5494
5495
5496
5497
5498
5499
5500
5501
5502
5503
5504
5505
5506
5507
5508
5509
5510
5511
5512
5513
5514
5515
5516
5517
5518
5519
5520
5521
5522
5523
5524
5525
5526
5527
5528
5529
5530
5531
5532
5533
5534
5535
5536
5537
5538
5539
5540
5541
5542
5543
5544
5545
5546
5547
5548
5549
5550
5551
5552
5553
5554
5555
5556
5557
5558
5559
5560
5561
5562
5563
5564
5565
5566
5567
5568
5569
5570
5571
5572
5573
5574
5575
5576
5577
5578
5579
5580
5581
5582
5583
5584
5585
5586
5587
5588
5589
5590
5591
5592
5593
5594
5595
5596
5597
5598
5599
5600
5601
5602
5603
5604
5605
5606
5607
5608
5609
5610
5611
5612
5613
5614
5615
5616
5617
5618
5619
5620
5621
5622
5623
5624
5625
5626
5627
5628
5629
5630
5631
5632
5633
5634
5635
5636
5637
5638
5639
5640
5641
5642
5643
5644
5645
5646
5647
5648
5649
5650
5651
5652
5653
5654
5655
5656
5657
5658
5659
5660
5661
5662
5663
5664
5665
5666
5667
5668
5669
5670
5671
5672
5673
5674
5675
5676
5677
5678
5679
5680
5681
5682
5683
5684
5685
5686
5687
5688
5689
5690
5691
5692
5693
5694
5695
5696
5697
5698
5699
5700
5701
5702
5703
5704
5705
5706
5707
5708
5709
5710
5711
5712
5713
5714
5715
5716
5717
5718
5719
5720
5721
5722
5723
5724
5725
5726
5727
5728
5729
5730
5731
5732
5733
5734
5735
5736
5737
5738
5739
5740
5741
5742
5743
5744
5745
5746
5747
5748
5749
5750
5751
5752
5753
5754
5755
5756
5757
5758
5759
5760
5761
5762
5763
5764
5765
5766
5767
5768
5769
5770
5771
5772
5773
5774
5775
5776
5777
5778
5779
5780
5781
5782
5783
5784
5785
5786
5787
5788
5789
5790
5791
5792
5793
5794
5795
5796
5797
5798
5799
5800
5801
5802
5803
5804
5805
5806
5807
5808
5809
5810
5811
5812
5813
5814
5815
5816
5817
5818
5819
5820
5821
5822
5823
5824
5825
5826
5827
5828
5829
5830
5831
5832
5833
5834
5835
5836
5837
5838
5839
5840
5841
5842
5843
5844
5845
5846
5847
5848
5849
5850
5851
5852
5853
5854
5855
5856
5857
5858
5859
5860
5861
5862
5863
5864
5865
5866
5867
5868
5869
5870
5871
5872
5873
5874
5875
5876
5877
5878
5879
5880
5881
5882
5883
5884
5885
5886
5887
5888
5889
5890
5891
5892
5893
5894
5895
5896
5897
5898
5899
5900
5901
5902
5903
5904
5905
5906
5907
5908
5909
5910
5911
5912
5913
5914
5915
5916
5917
5918
5919
5920
5921
5922
5923
5924
5925
5926
5927
5928
5929
5930
5931
5932
5933
5934
5935
5936
5937
5938
5939
5940
5941
5942
5943
5944
5945
5946
5947
5948
5949
5950
5951
5952
5953
5954
5955
5956
5957
5958
5959
5960
5961
5962
5963
5964
5965
5966
5967
5968
5969
5970
5971
5972
5973
5974
5975
5976
5977
5978
5979
5980
5981
5982
5983
5984
5985
5986
5987
5988
5989
5990
5991
5992
5993
5994
5995
5996
5997
5998
5999
6000
6001
6002
6003
6004
6005
6006
6007
6008
6009
6010
6011
6012
6013
6014
6015
6016
6017
6018
6019
6020
6021
6022
6023
6024
6025
6026
6027
6028
6029
6030
6031
6032
6033
6034
6035
6036
6037
6038
6039
6040
6041
6042
6043
6044
6045
6046
6047
6048
6049
6050
6051
6052
6053
6054
6055
6056
6057
6058
6059
6060
6061
6062
6063
6064
6065
6066
6067
6068
6069
6070
6071
6072
6073
6074
6075
6076
6077
6078
6079
6080
6081
6082
6083
6084
6085
6086
6087
6088
6089
6090
6091
6092
6093
6094
6095
6096
6097
6098
6099
6100
6101
6102
6103
6104
6105
6106
6107
6108
6109
6110
6111
6112
6113
6114
6115
6116
6117
6118
6119
6120
6121
6122
6123
6124
6125
6126
6127
6128
6129
6130
6131
6132
6133
6134
6135
6136
6137
6138
6139
6140
6141
6142
6143
6144
6145
6146
6147
6148
6149
6150
6151
6152
6153
6154
6155
6156
6157
6158
6159
6160
6161
6162
6163
6164
6165
6166
6167
6168
6169
6170
6171
6172
6173
6174
6175
6176
6177
6178
6179
6180
6181
6182
6183
6184
6185
6186
6187
6188
6189
6190
6191
6192
6193
6194
6195
6196
6197
6198
6199
6200
6201
6202
6203
6204
6205
6206
6207
6208
6209
6210
6211
6212
6213
6214
6215
6216
6217
6218
6219
6220
6221
6222
6223
6224
6225
6226
6227
6228
6229
6230
6231
6232
6233
6234
6235
6236
6237
6238
6239
6240
6241
6242
6243
6244
6245
6246
6247
6248
6249
6250
6251
6252
6253
6254
6255
6256
6257
6258
6259
6260
6261
6262
6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
6273
6274
6275
6276
6277
6278
6279
6280
6281
6282
6283
6284
6285
6286
6287
6288
6289
6290
6291
6292
6293
6294
6295
6296
6297
6298
6299
6300
6301
6302
6303
6304
6305
6306
6307
6308
6309
6310
6311
6312
6313
6314
6315
6316
6317
6318
6319
6320
6321
6322
6323
6324
6325
6326
6327
6328
6329
6330
6331
6332
6333
6334
6335
6336
6337
6338
6339
6340
6341
6342
6343
6344
6345
6346
6347
6348
6349
6350
6351
6352
6353
6354
6355
6356
6357
6358
6359
6360
6361
6362
6363
6364
6365
6366
6367
6368
6369
6370
6371
6372
6373
6374
6375
6376
6377
6378
6379
6380
6381
6382
6383
6384
6385
6386
6387
6388
6389
6390
6391
6392
6393
6394
6395
6396
6397
6398
6399
6400
6401
6402
6403
6404
6405
6406
6407
6408
6409
6410
6411
6412
6413
6414
6415
6416
6417
6418
6419
6420
6421
6422
6423
6424
6425
6426
6427
6428
6429
6430
6431
6432
6433
6434
6435
6436
6437
6438
6439
6440
6441
6442
6443
6444
6445
6446
6447
6448
6449
6450
6451
6452
6453
6454
6455
6456
6457
6458
6459
6460
6461
6462
6463
6464
6465
6466
6467
6468
6469
6470
6471
6472
6473
6474
6475
6476
6477
6478
6479
6480
6481
6482
6483
6484
6485
6486
6487
6488
6489
6490
6491
6492
6493
6494
6495
6496
6497
6498
6499
6500
6501
6502
6503
6504
6505
6506
6507
6508
6509
6510
6511
6512
6513
6514
6515
6516
6517
6518
6519
6520
6521
6522
6523
6524
6525
6526
6527
6528
6529
6530
6531
6532
6533
6534
6535
6536
6537
6538
6539
6540
6541
6542
6543
6544
6545
6546
6547
6548
6549
6550
6551
6552
6553
6554
6555
6556
6557
6558
6559
6560
6561
6562
6563
6564
6565
6566
6567
6568
6569
6570
6571
6572
6573
6574
6575
6576
6577
6578
6579
6580
6581
6582
6583
6584
6585
6586
6587
6588
6589
6590
6591
6592
6593
6594
6595
6596
6597
6598
6599
6600
6601
6602
6603
6604
6605
6606
6607
6608
6609
6610
6611
6612
6613
6614
6615
6616
6617
6618
6619
6620
6621
6622
6623
6624
6625
6626
6627
6628
6629
6630
6631
6632
6633
6634
6635
6636
6637
6638
6639
6640
6641
6642
6643
6644
6645
6646
6647
6648
6649
6650
6651
6652
6653
6654
6655
6656
6657
6658
6659
6660
6661
6662
6663
6664
6665
6666
6667
6668
6669
6670
6671
6672
6673
6674
6675
6676
6677
6678
6679
6680
6681
6682
6683
6684
6685
6686
6687
6688
6689
6690
6691
6692
6693
6694
6695
6696
6697
6698
6699
6700
6701
6702
6703
6704
6705
6706
6707
6708
6709
6710
6711
6712
6713
6714
6715
6716
6717
6718
6719
6720
6721
6722
6723
6724
6725
6726
6727
6728
6729
6730
6731
6732
6733
6734
6735
6736
6737
6738
6739
6740
6741
6742
6743
6744
6745
6746
6747
6748
6749
6750
6751
6752
6753
6754
6755
6756
6757
6758
6759
6760
6761
6762
6763
6764
6765
6766
6767
6768
6769
6770
6771
6772
6773
6774
6775
6776
6777
6778
6779
6780
6781
6782
6783
6784
6785
6786
6787
6788
6789
6790
6791
6792
6793
6794
6795
6796
6797
6798
6799
6800
6801
6802
6803
6804
6805
6806
6807
6808
6809
6810
6811
6812
6813
6814
6815
6816
6817
6818
6819
6820
6821
6822
6823
6824
6825
6826
6827
6828
6829
6830
6831
6832
6833
6834
6835
6836
6837
6838
6839
6840
6841
6842
6843
6844
6845
6846
6847
6848
6849
6850
6851
6852
6853
6854
6855
6856
6857
6858
6859
6860
6861
6862
6863
6864
6865
6866
6867
6868
6869
6870
6871
6872
6873
6874
6875
6876
6877
6878
6879
6880
6881
6882
6883
6884
6885
6886
6887
6888
6889
6890
6891
6892
6893
6894
6895
6896
6897
6898
6899
6900
6901
6902
6903
6904
6905
6906
6907
6908
6909
6910
6911
6912
6913
6914
6915
6916
6917
6918
6919
6920
6921
6922
6923
6924
6925
6926
6927
6928
6929
6930
6931
6932
6933
6934
6935
6936
6937
6938
6939
6940
6941
6942
6943
6944
6945
6946
6947
6948
6949
6950
6951
6952
6953
6954
6955
6956
6957
6958
6959
6960
6961
6962
6963
6964
6965
6966
6967
6968
6969
6970
6971
6972
6973
6974
6975
6976
6977
6978
6979
6980
6981
6982
6983
6984
6985
6986
6987
6988
6989
6990
6991
6992
6993
6994
6995
6996
6997
6998
6999
7000
7001
7002
7003
7004
7005
7006
7007
7008
7009
7010
7011
7012
7013
7014
7015
7016
7017
7018
7019
7020
7021
7022
7023
7024
7025
7026
7027
7028
7029
7030
7031
7032
7033
7034
7035
7036
7037
7038
7039
7040
7041
7042
7043
7044
7045
7046
7047
7048
7049
7050
7051
7052
7053
7054
7055
7056
7057
7058
7059
7060
7061
7062
7063
7064
7065
7066
7067
7068
7069
7070
7071
7072
7073
7074
7075
7076
7077
7078
7079
7080
7081
7082
7083
7084
7085
7086
7087
7088
7089
7090
7091
7092
7093
7094
7095
7096
7097
7098
7099
7100
7101
7102
7103
7104
7105
7106
7107
7108
7109
7110
7111
7112
7113
7114
7115
7116
7117
7118
7119
7120
7121
7122
7123
7124
7125
7126
7127
7128
7129
7130
7131
7132
7133
7134
7135
7136
7137
7138
7139
7140
7141
7142
7143
7144
7145
7146
7147
7148
7149
7150
7151
7152
7153
7154
7155
7156
7157
7158
7159
7160
7161
7162
7163
7164
7165
7166
7167
7168
7169
7170
7171
7172
7173
7174
7175
7176
7177
7178
7179
7180
7181
7182
7183
7184
7185
7186
7187
7188
7189
7190
7191
7192
7193
7194
7195
7196
7197
7198
7199
7200
7201
7202
7203
7204
7205
7206
7207
7208
7209
7210
7211
7212
7213
7214
7215
7216
7217
7218
7219
7220
7221
7222
7223
7224
7225
7226
7227
7228
7229
7230
7231
7232
7233
7234
7235
7236
7237
7238
7239
7240
7241
7242
7243
7244
7245
7246
7247
7248
7249
7250
7251
7252
7253
7254
7255
7256
7257
7258
7259
7260
7261
7262
7263
7264
7265
7266
7267
7268
7269
7270
7271
7272
7273
7274
7275
7276
7277
7278
7279
7280
7281
7282
7283
7284
7285
7286
7287
7288
7289
7290
7291
7292
7293
7294
7295
7296
7297
7298
7299
7300
7301
7302
7303
7304
7305
7306
7307
7308
7309
7310
7311
7312
7313
7314
7315
7316
7317
7318
7319
7320
7321
7322
7323
7324
7325
7326
7327
7328
7329
7330
7331
7332
7333
7334
7335
7336
7337
7338
7339
7340
7341
7342
7343
7344
7345
7346
7347
7348
7349
7350
7351
7352
7353
7354
7355
7356
7357
7358
7359
7360
7361
7362
7363
7364
7365
7366
7367
7368
7369
7370
7371
7372
7373
7374
7375
7376
7377
7378
7379
7380
7381
7382
7383
7384
7385
7386
7387
7388
7389
7390
7391
7392
7393
7394
7395
7396
7397
7398
7399
7400
7401
7402
7403
7404
7405
7406
7407
7408
7409
7410
7411
7412
7413
7414
7415
7416
7417
7418
7419
7420
7421
7422
7423
7424
7425
7426
7427
7428
7429
7430
7431
7432
7433
7434
7435
7436
7437
7438
7439
7440
7441
7442
7443
7444
7445
7446
7447
7448
7449
7450
7451
7452
7453
7454
7455
7456
7457
7458
7459
7460
7461
7462
7463
7464
7465
7466
7467
7468
7469
7470
7471
7472
7473
7474
7475
7476
7477
7478
7479
7480
7481
7482
7483
7484
7485
7486
7487
7488
7489
7490
7491
7492
7493
7494
7495
7496
7497
7498
7499
7500
7501
7502
7503
7504
7505
7506
7507
7508
7509
7510
7511
7512
7513
7514
7515
7516
7517
7518
7519
7520
7521
7522
7523
7524
7525
7526
7527
7528
7529
7530
7531
7532
7533
7534
7535
7536
7537
7538
7539
7540
7541
7542
7543
7544
7545
7546
7547
7548
7549
7550
7551
7552
7553
7554
7555
7556
7557
7558
7559
7560
7561
7562
7563
7564
7565
7566
7567
7568
7569
7570
7571
7572
7573
7574
7575
7576
7577
7578
7579
7580
7581
7582
7583
7584
7585
7586
7587
7588
7589
7590
7591
7592
7593
7594
7595
7596
7597
7598
7599
7600
7601
7602
7603
7604
7605
7606
7607
7608
7609
7610
7611
7612
7613
7614
7615
7616
7617
7618
7619
7620
7621
7622
7623
7624
7625
7626
7627
7628
7629
7630
7631
7632
7633
7634
7635
7636
7637
7638
7639
7640
7641
7642
7643
7644
7645
7646
7647
7648
7649
7650
7651
7652
7653
7654
7655
7656
7657
7658
7659
7660
7661
7662
7663
7664
7665
7666
7667
7668
7669
7670
7671
7672
7673
7674
7675
7676
7677
7678
7679
7680
7681
7682
7683
7684
7685
7686
7687
7688
7689
7690
7691
7692
7693
7694
7695
7696
7697
7698
7699
7700
7701
7702
7703
7704
7705
7706
7707
7708
7709
7710
7711
7712
7713
7714
7715
7716
7717
7718
7719
7720
7721
7722
7723
7724
7725
7726
7727
7728
7729
7730
7731
7732
7733
7734
7735
7736
7737
7738
7739
7740
7741
7742
7743
7744
7745
7746
7747
7748
7749
7750
7751
7752
7753
7754
7755
7756
7757
7758
7759
7760
7761
7762
7763
7764
7765
7766
7767
7768
7769
7770
7771
7772
7773
7774
7775
7776
7777
7778
7779
7780
7781
7782
7783
7784
7785
7786
7787
7788
7789
7790
7791
7792
7793
7794
7795
7796
7797
7798
7799
7800
7801
7802
7803
7804
7805
7806
7807
7808
7809
7810
7811
7812
7813
7814
7815
7816
7817
7818
7819
7820
7821
7822
7823
7824
7825
7826
7827
7828
7829
7830
7831
7832
7833
7834
7835
7836
7837
7838
7839
7840
7841
7842
7843
7844
7845
7846
7847
7848
7849
7850
7851
7852
7853
7854
7855
7856
7857
7858
7859
7860
7861
7862
7863
7864
7865
7866
7867
7868
7869
7870
7871
7872
7873
7874
7875
7876
7877
7878
7879
7880
7881
7882
7883
7884
7885
7886
7887
7888
7889
7890
7891
7892
7893
7894
7895
7896
7897
7898
7899
7900
7901
7902
7903
7904
7905
7906
7907
7908
7909
7910
7911
7912
7913
7914
7915
7916
7917
7918
7919
7920
7921
7922
7923
7924
7925
7926
7927
7928
7929
7930
7931
7932
7933
7934
7935
7936
7937
7938
7939
7940
7941
7942
7943
7944
7945
7946
7947
7948
7949
7950
7951
7952
7953
7954
7955
7956
7957
7958
7959
7960
7961
7962
7963
7964
7965
7966
7967
7968
7969
7970
7971
7972
7973
7974
7975
7976
7977
7978
7979
7980
7981
7982
7983
7984
7985
7986
7987
7988
7989
7990
7991
7992
7993
7994
7995
7996
7997
7998
7999
8000
8001
8002
8003
8004
8005
8006
8007
8008
8009
8010
8011
8012
8013
8014
8015
8016
8017
8018
8019
8020
8021
8022
8023
8024
8025
8026
8027
8028
8029
8030
8031
8032
8033
8034
8035
8036
8037
8038
8039
8040
8041
8042
8043
8044
8045
8046
8047
8048
8049
8050
8051
8052
8053
8054
8055
8056
8057
8058
8059
8060
8061
8062
8063
8064
8065
8066
8067
8068
8069
8070
8071
8072
8073
8074
8075
8076
8077
8078
8079
8080
8081
8082
8083
8084
8085
8086
8087
8088
8089
8090
8091
8092
8093
8094
8095
8096
8097
8098
8099
8100
8101
8102
8103
8104
8105
8106
8107
8108
8109
8110
8111
8112
8113
8114
8115
8116
8117
8118
8119
8120
8121
8122
8123
8124
8125
8126
8127
8128
8129
8130
8131
8132
8133
8134
8135
8136
8137
8138
8139
8140
8141
8142
8143
8144
8145
8146
8147
8148
8149
8150
8151
8152
8153
8154
8155
8156
8157
8158
8159
8160
8161
8162
8163
8164
8165
8166
8167
8168
8169
8170
8171
8172
8173
8174
8175
8176
8177
8178
8179
8180
8181
8182
8183
8184
8185
8186
8187
8188
8189
8190
8191
8192
8193
8194
8195
8196
8197
8198
8199
8200
8201
8202
8203
8204
8205
8206
8207
8208
8209
8210
8211
8212
8213
8214
8215
8216
8217
8218
8219
8220
8221
8222
8223
8224
8225
8226
8227
8228
8229
8230
8231
8232
8233
8234
8235
8236
8237
8238
8239
8240
8241
8242
8243
8244
8245
8246
8247
8248
8249
8250
8251
8252
8253
8254
8255
8256
8257
8258
8259
8260
8261
8262
8263
8264
8265
8266
8267
8268
8269
8270
8271
8272
8273
8274
8275
8276
8277
8278
8279
8280
8281
8282
8283
8284
8285
8286
8287
8288
8289
8290
8291
8292
8293
8294
8295
8296
8297
8298
8299
8300
8301
8302
8303
8304
8305
8306
8307
8308
8309
8310
8311
8312
8313
8314
8315
8316
8317
8318
8319
8320
8321
8322
8323
8324
8325
8326
8327
8328
8329
8330
8331
8332
8333
8334
8335
8336
8337
8338
8339
8340
8341
8342
8343
8344
8345
8346
8347
8348
8349
8350
8351
8352
8353
8354
8355
8356
8357
8358
8359
8360
8361
8362
8363
8364
8365
8366
8367
8368
8369
8370
8371
8372
8373
8374
8375
8376
8377
8378
8379
8380
8381
8382
8383
8384
8385
8386
8387
8388
8389
8390
8391
8392
8393
8394
8395
8396
8397
8398
8399
8400
8401
8402
8403
8404
8405
8406
8407
8408
8409
8410
8411
8412
8413
8414
8415
8416
8417
8418
8419
8420
8421
8422
8423
8424
8425
8426
8427
8428
8429
8430
8431
8432
8433
8434
8435
8436
8437
8438
8439
8440
8441
8442
8443
8444
8445
8446
8447
8448
8449
8450
8451
8452
8453
8454
8455
8456
8457
8458
8459
8460
8461
8462
8463
8464
8465
8466
8467
8468
8469
8470
8471
8472
8473
8474
8475
8476
8477
8478
8479
8480
8481
8482
8483
8484
8485
8486
8487
8488
8489
8490
8491
8492
8493
8494
8495
8496
8497
8498
8499
8500
8501
8502
8503
8504
8505
8506
8507
8508
8509
8510
8511
8512
8513
8514
8515
8516
8517
8518
8519
8520
8521
8522
8523
8524
8525
8526
8527
8528
8529
8530
8531
8532
8533
8534
8535
8536
8537
8538
8539
8540
8541
8542
8543
8544
8545
8546
8547
8548
8549
8550
8551
8552
8553
8554
8555
8556
8557
8558
8559
8560
8561
8562
8563
8564
8565
8566
8567
8568
8569
8570
8571
8572
8573
8574
8575
8576
8577
8578
8579
8580
8581
8582
8583
8584
8585
8586
8587
8588
8589
8590
8591
8592
8593
8594
8595
8596
8597
8598
8599
8600
8601
8602
8603
8604
8605
8606
8607
8608
8609
8610
8611
8612
8613
8614
8615
8616
8617
8618
8619
8620
8621
8622
8623
8624
8625
8626
8627
8628
8629
8630
8631
8632
8633
8634
8635
8636
8637
8638
8639
8640
8641
8642
8643
8644
8645
8646
8647
8648
8649
8650
8651
8652
8653
8654
8655
8656
8657
8658
8659
8660
8661
8662
8663
8664
8665
8666
8667
8668
8669
8670
8671
8672
8673
8674
8675
8676
8677
8678
8679
8680
8681
8682
8683
8684
8685
8686
8687
8688
8689
8690
8691
8692
8693
8694
8695
8696
8697
8698
8699
8700
8701
8702
8703
8704
8705
8706
8707
8708
8709
8710
8711
8712
8713
8714
8715
8716
8717
8718
8719
8720
8721
8722
8723
8724
8725
8726
8727
8728
8729
8730
8731
8732
8733
8734
8735
8736
8737
8738
8739
8740
8741
8742
8743
8744
8745
8746
8747
8748
8749
8750
8751
8752
8753
8754
8755
8756
8757
8758
8759
8760
8761
8762
8763
8764
8765
8766
8767
8768
8769
8770
8771
8772
8773
8774
8775
8776
8777
8778
8779
8780
8781
8782
8783
8784
8785
8786
8787
8788
8789
8790
8791
8792
8793
8794
8795
8796
8797
8798
8799
8800
8801
8802
8803
8804
8805
8806
8807
8808
8809
8810
8811
8812
8813
8814
8815
8816
8817
8818
8819
8820
8821
8822
8823
8824
8825
8826
8827
8828
8829
8830
8831
8832
8833
8834
8835
8836
8837
8838
8839
8840
8841
8842
8843
8844
8845
8846
8847
8848
8849
8850
8851
8852
8853
8854
8855
8856
8857
8858
8859
8860
8861
8862
8863
8864
8865
8866
8867
8868
8869
8870
8871
8872
8873
8874
8875
8876
8877
8878
8879
8880
8881
8882
8883
8884
8885
8886
8887
8888
8889
8890
8891
8892
8893
8894
8895
8896
8897
8898
8899
8900
8901
8902
8903
8904
8905
8906
8907
8908
8909
8910
8911
8912
8913
8914
8915
8916
8917
8918
8919
8920
8921
8922
8923
8924
8925
8926
8927
8928
8929
8930
8931
8932
8933
8934
8935
8936
8937
8938
8939
8940
8941
8942
8943
8944
8945
8946
8947
8948
8949
8950
8951
8952
8953
8954
8955
8956
8957
8958
8959
8960
8961
8962
8963
8964
8965
8966
8967
8968
8969
8970
8971
8972
8973
8974
8975
8976
8977
8978
8979
8980
8981
8982
8983
8984
8985
8986
8987
8988
8989
8990
8991
8992
8993
8994
8995
8996
8997
8998
8999
9000
9001
9002
9003
9004
9005
9006
9007
9008
9009
9010
9011
9012
9013
9014
9015
9016
9017
9018
9019
9020
9021
9022
9023
9024
9025
9026
9027
9028
9029
9030
9031
9032
9033
9034
9035
9036
9037
9038
9039
9040
9041
9042
9043
9044
9045
9046
9047
9048
9049
9050
9051
9052
9053
9054
9055
9056
9057
9058
9059
9060
9061
9062
9063
9064
9065
9066
9067
9068
9069
9070
9071
9072
9073
9074
9075
9076
9077
9078
9079
9080
9081
9082
9083
9084
9085
9086
9087
9088
9089
9090
9091
9092
9093
9094
9095
9096
9097
9098
9099
9100
9101
9102
9103
9104
9105
9106
9107
9108
9109
9110
9111
9112
9113
9114
9115
9116
9117
9118
9119
9120
9121
9122
9123
9124
9125
9126
9127
9128
9129
9130
9131
9132
9133
9134
9135
9136
9137
9138
9139
9140
9141
9142
9143
9144
9145
9146
9147
9148
9149
9150
9151
9152
9153
9154
9155
9156
9157
9158
9159
9160
9161
9162
9163
9164
9165
9166
9167
9168
9169
9170
9171
9172
9173
9174
9175
9176
9177
9178
9179
9180
9181
9182
9183
9184
9185
9186
9187
9188
9189
9190
9191
9192
9193
9194
9195
9196
9197
9198
9199
9200
9201
9202
9203
9204
9205
9206
9207
9208
9209
9210
9211
9212
9213
9214
9215
9216
9217
9218
9219
9220
9221
9222
9223
9224
9225
9226
9227
9228
9229
9230
9231
9232
9233
9234
9235
9236
9237
9238
9239
9240
9241
9242
9243
9244
9245
9246
9247
9248
9249
9250
9251
9252
9253
9254
9255
9256
9257
9258
9259
9260
9261
9262
9263
9264
9265
9266
9267
9268
9269
9270
9271
9272
9273
9274
9275
9276
9277
9278
9279
9280
9281
9282
9283
9284
9285
9286
9287
9288
9289
9290
9291
9292
9293
9294
9295
9296
9297
9298
9299
9300
9301
9302
9303
9304
9305
9306
9307
9308
9309
9310
9311
9312
9313
9314
9315
9316
9317
9318
9319
9320
9321
9322
9323
9324
9325
9326
9327
9328
9329
9330
9331
9332
9333
9334
9335
9336
9337
9338
9339
9340
9341
9342
9343
9344
9345
9346
9347
9348
9349
9350
9351
9352
9353
9354
9355
9356
9357
9358
9359
9360
9361
9362
9363
9364
9365
9366
9367
9368
9369
9370
9371
9372
9373
9374
9375
9376
9377
9378
9379
9380
9381
9382
9383
9384
9385
9386
9387
9388
9389
9390
9391
9392
9393
9394
9395
9396
9397
9398
9399
9400
9401
9402
9403
9404
9405
9406
9407
9408
9409
9410
9411
9412
9413
9414
9415
9416
9417
9418
9419
9420
9421
9422
9423
9424
9425
9426
9427
9428
9429
9430
9431
9432
9433
9434
9435
9436
9437
9438
9439
9440
9441
9442
9443
9444
9445
9446
9447
9448
9449
9450
9451
9452
9453
9454
9455
9456
9457
9458
9459
9460
9461
9462
9463
9464
9465
9466
9467
9468
9469
9470
9471
9472
9473
9474
9475
9476
9477
9478
9479
9480
9481
9482
9483
9484
9485
9486
9487
9488
9489
9490
9491
9492
9493
9494
9495
9496
9497
9498
9499
9500
9501
9502
9503
9504
9505
9506
9507
9508
9509
9510
9511
9512
9513
9514
9515
9516
9517
9518
9519
9520
9521
9522
9523
9524
9525
9526
9527
9528
9529
9530
9531
9532
9533
9534
9535
9536
9537
9538
9539
9540
9541
9542
9543
9544
9545
9546
9547
9548
9549
9550
9551
9552
9553
9554
9555
9556
9557
9558
9559
9560
9561
9562
9563
9564
9565
9566
9567
9568
9569
9570
9571
9572
9573
9574
9575
9576
9577
9578
9579
9580
9581
9582
9583
9584
9585
9586
9587
9588
9589
9590
9591
9592
9593
9594
9595
9596
9597
9598
9599
9600
9601
9602
9603
9604
9605
9606
9607
9608
9609
9610
9611
9612
9613
9614
9615
9616
9617
9618
9619
9620
9621
9622
9623
9624
9625
9626
9627
9628
9629
9630
9631
9632
9633
9634
9635
9636
9637
9638
9639
9640
9641
9642
9643
9644
9645
9646
9647
9648
9649
9650
9651
9652
9653
9654
9655
9656
9657
9658
9659
9660
9661
9662
9663
9664
9665
9666
9667
9668
9669
9670
9671
9672
9673
9674
9675
9676
9677
9678
9679
9680
9681
9682
9683
9684
9685
9686
9687
9688
9689
9690
9691
9692
9693
9694
9695
9696
9697
9698
9699
9700
9701
9702
9703
9704
9705
9706
9707
9708
9709
9710
9711
9712
9713
9714
9715
9716
9717
9718
9719
9720
9721
9722
9723
9724
9725
9726
9727
9728
9729
9730
9731
9732
9733
9734
9735
9736
9737
9738
9739
9740
9741
9742
9743
9744
9745
9746
9747
9748
9749
9750
9751
9752
9753
9754
9755
9756
9757
9758
9759
9760
9761
9762
9763
9764
9765
9766
9767
9768
9769
9770
9771
9772
9773
9774
9775
9776
9777
9778
9779
9780
9781
9782
9783
9784
9785
9786
9787
9788
9789
9790
9791
9792
9793
9794
9795
9796
9797
9798
9799
9800
9801
9802
9803
9804
9805
9806
9807
9808
9809
9810
9811
9812
9813
9814
9815
9816
9817
9818
9819
9820
9821
9822
9823
9824
9825
9826
9827
9828
9829
9830
9831
9832
9833
9834
9835
9836
9837
9838
9839
9840
9841
9842
9843
9844
9845
9846
9847
9848
9849
9850
9851
9852
9853
9854
9855
9856
9857
9858
9859
9860
9861
9862
9863
9864
9865
9866
9867
9868
9869
9870
9871
9872
9873
9874
9875
9876
9877
9878
9879
9880
9881
9882
9883
9884
9885
9886
9887
9888
9889
9890
9891
9892
9893
9894
9895
9896
9897
9898
9899
9900
9901
9902
9903
9904
9905
9906
9907
9908
9909
9910
9911
9912
9913
9914
9915
9916
9917
9918
9919
9920
9921
9922
9923
9924
9925
9926
9927
9928
9929
9930
9931
9932
9933
9934
9935
9936
9937
9938
9939
9940
9941
9942
9943
9944
9945
9946
9947
9948
9949
9950
9951
9952
9953
9954
9955
9956
9957
9958
9959
9960
9961
9962
9963
9964
9965
9966
9967
9968
9969
9970
9971
9972
9973
9974
9975
9976
9977
9978
9979
9980
9981
9982
9983
9984
9985
9986
9987
9988
9989
9990
9991
9992
9993
9994
9995
9996
9997
9998
9999
10000
10001
10002
10003
10004
10005
10006
10007
10008
10009
10010
10011
10012
10013
10014
10015
10016
10017
10018
10019
10020
10021
10022
10023
10024
10025
10026
10027
10028
10029
10030
10031
10032
10033
10034
10035
10036
10037
10038
10039
10040
10041
10042
10043
10044
10045
10046
10047
10048
10049
10050
10051
10052
10053
10054
10055
10056
10057
10058
10059
10060
10061
10062
10063
10064
10065
10066
10067
10068
10069
10070
10071
10072
10073
10074
10075
10076
10077
10078
10079
10080
10081
10082
10083
10084
10085
10086
10087
10088
10089
10090
10091
10092
10093
10094
10095
10096
10097
10098
10099
10100
10101
10102
10103
10104
10105
10106
10107
10108
10109
10110
10111
10112
10113
10114
10115
10116
10117
10118
10119
10120
10121
10122
10123
10124
10125
10126
10127
10128
10129
10130
10131
10132
10133
10134
10135
10136
10137
10138
10139
10140
10141
10142
10143
10144
10145
10146
10147
10148
10149
10150
10151
10152
10153
10154
10155
10156
10157
10158
10159
10160
10161
10162
10163
10164
10165
10166
10167
10168
10169
10170
10171
10172
10173
10174
10175
10176
10177
10178
10179
10180
10181
10182
10183
10184
10185
10186
10187
10188
10189
10190
10191
10192
10193
10194
10195
10196
10197
10198
10199
10200
10201
10202
10203
10204
10205
10206
10207
10208
10209
10210
10211
10212
10213
10214
10215
10216
10217
10218
10219
10220
10221
10222
10223
10224
10225
10226
10227
10228
10229
10230
10231
10232
10233
10234
10235
10236
10237
10238
10239
10240
10241
10242
10243
10244
10245
10246
10247
10248
10249
10250
10251
10252
10253
10254
10255
10256
10257
10258
10259
10260
10261
10262
10263
10264
10265
10266
10267
10268
10269
10270
10271
10272
10273
10274
10275
10276
10277
10278
10279
10280
10281
10282
10283
10284
10285
10286
10287
10288
10289
10290
10291
10292
10293
10294
10295
10296
10297
10298
10299
10300
10301
10302
10303
10304
10305
10306
10307
10308
10309
10310
10311
10312
10313
10314
10315
10316
10317
10318
10319
10320
10321
10322
10323
10324
10325
10326
10327
10328
10329
10330
10331
10332
10333
10334
10335
10336
10337
10338
10339
10340
10341
10342
10343
10344
10345
10346
10347
10348
10349
10350
10351
10352
10353
10354
10355
10356
10357
10358
10359
10360
10361
10362
10363
10364
10365
10366
10367
10368
10369
10370
10371
10372
10373
10374
10375
10376
10377
10378
10379
10380
10381
10382
10383
10384
10385
10386
10387
10388
10389
10390
10391
10392
10393
10394
10395
10396
10397
10398
10399
10400
10401
10402
10403
10404
10405
10406
10407
10408
10409
10410
10411
10412
10413
10414
10415
10416
10417
10418
10419
10420
10421
10422
10423
10424
10425
10426
10427
10428
10429
10430
10431
10432
10433
10434
10435
10436
10437
10438
10439
10440
10441
10442
10443
10444
10445
10446
10447
10448
10449
10450
10451
10452
10453
10454
10455
10456
10457
10458
10459
10460
10461
10462
10463
10464
10465
10466
10467
10468
10469
10470
10471
10472
10473
10474
10475
10476
10477
10478
10479
10480
10481
10482
10483
10484
10485
10486
10487
10488
10489
10490
10491
10492
10493
10494
10495
10496
10497
10498
10499
10500
10501
10502
10503
10504
10505
10506
10507
10508
10509
10510
10511
10512
10513
10514
10515
10516
10517
10518
10519
10520
10521
10522
10523
10524
10525
10526
10527
10528
10529
10530
10531
10532
10533
10534
10535
10536
10537
10538
10539
10540
10541
10542
10543
10544
10545
10546
10547
10548
10549
10550
10551
10552
10553
10554
10555
10556
10557
10558
10559
10560
10561
10562
10563
10564
10565
10566
10567
10568
10569
10570
10571
10572
10573
10574
10575
10576
10577
10578
10579
10580
10581
10582
10583
10584
10585
10586
10587
10588
10589
10590
10591
10592
10593
10594
10595
10596
10597
10598
10599
10600
10601
10602
10603
10604
10605
10606
10607
10608
10609
10610
10611
10612
10613
10614
10615
10616
10617
10618
10619
10620
10621
10622
10623
10624
10625
10626
10627
10628
10629
10630
10631
10632
10633
10634
10635
10636
10637
10638
10639
10640
10641
10642
10643
10644
10645
10646
10647
10648
10649
10650
10651
10652
10653
10654
10655
10656
10657
10658
10659
10660
10661
10662
10663
10664
10665
10666
10667
10668
10669
10670
10671
10672
10673
10674
10675
10676
10677
10678
10679
10680
10681
10682
10683
10684
10685
10686
10687
10688
10689
10690
10691
10692
10693
10694
10695
10696
10697
10698
10699
10700
10701
10702
10703
10704
10705
10706
10707
10708
10709
10710
10711
10712
10713
10714
10715
10716
10717
10718
10719
10720
10721
10722
10723
10724
10725
10726
10727
10728
10729
10730
10731
10732
10733
10734
10735
10736
10737
10738
10739
10740
10741
10742
10743
10744
10745
10746
10747
10748
10749
10750
10751
10752
10753
10754
10755
10756
10757
10758
10759
10760
10761
10762
10763
10764
10765
10766
10767
10768
10769
10770
10771
10772
10773
10774
10775
10776
10777
10778
10779
10780
10781
10782
10783
10784
10785
10786
10787
10788
10789
10790
10791
10792
10793
10794
10795
10796
10797
10798
10799
10800
10801
10802
10803
10804
10805
10806
10807
10808
10809
10810
10811
10812
10813
10814
10815
10816
10817
10818
10819
10820
10821
10822
10823
10824
10825
10826
10827
10828
10829
10830
10831
10832
10833
10834
10835
10836
10837
10838
10839
10840
10841
10842
10843
10844
10845
10846
10847
10848
10849
10850
10851
10852
10853
10854
10855
10856
10857
10858
10859
10860
10861
10862
10863
10864
10865
10866
10867
10868
10869
10870
10871
10872
10873
10874
10875
10876
10877
10878
10879
10880
10881
10882
10883
10884
10885
10886
10887
10888
10889
10890
10891
10892
10893
10894
10895
10896
10897
10898
10899
10900
10901
10902
10903
10904
10905
10906
10907
10908
10909
10910
10911
10912
10913
10914
10915
10916
10917
10918
10919
10920
10921
10922
10923
10924
10925
10926
10927
10928
10929
10930
10931
10932
10933
10934
10935
10936
10937
10938
10939
10940
10941
10942
10943
10944
10945
10946
10947
10948
10949
10950
10951
10952
10953
10954
10955
10956
10957
10958
10959
10960
10961
10962
10963
10964
10965
10966
10967
10968
10969
10970
10971
10972
10973
10974
10975
10976
10977
10978
10979
10980
10981
10982
10983
10984
10985
10986
10987
10988
10989
10990
10991
10992
10993
10994
10995
10996
10997
10998
10999
11000
11001
11002
11003
11004
11005
11006
11007
11008
11009
11010
11011
11012
11013
11014
11015
11016
11017
11018
11019
11020
11021
11022
11023
11024
11025
11026
11027
11028
11029
11030
11031
11032
11033
11034
11035
11036
11037
11038
11039
11040
11041
11042
11043
11044
11045
11046
11047
11048
11049
11050
11051
11052
11053
11054
11055
11056
11057
11058
11059
11060
11061
11062
11063
11064
11065
11066
11067
11068
11069
11070
11071
11072
11073
11074
11075
11076
11077
11078
11079
11080
11081
11082
11083
11084
11085
11086
11087
11088
11089
11090
11091
11092
11093
11094
11095
11096
11097
11098
11099
11100
11101
11102
11103
11104
11105
11106
11107
11108
11109
11110
11111
11112
11113
11114
11115
11116
11117
11118
11119
11120
11121
11122
11123
11124
11125
11126
11127
11128
11129
11130
11131
11132
11133
11134
11135
11136
11137
11138
11139
11140
11141
11142
11143
11144
11145
11146
11147
11148
11149
11150
11151
11152
11153
11154
11155
11156
11157
11158
11159
11160
11161
11162
11163
11164
11165
11166
11167
11168
11169
11170
11171
11172
11173
11174
11175
11176
11177
11178
11179
11180
11181
11182
11183
11184
11185
11186
11187
11188
11189
11190
11191
11192
11193
11194
11195
11196
11197
11198
11199
11200
11201
11202
11203
11204
11205
11206
11207
11208
11209
11210
11211
11212
11213
11214
11215
11216
11217
11218
11219
11220
11221
11222
11223
11224
11225
11226
11227
11228
11229
11230
11231
11232
11233
11234
11235
11236
11237
11238
11239
11240
11241
11242
11243
11244
11245
11246
11247
11248
11249
11250
11251
11252
11253
11254
11255
11256
11257
11258
11259
11260
11261
11262
11263
11264
11265
11266
11267
11268
11269
11270
11271
11272
11273
11274
11275
11276
11277
11278
11279
11280
11281
11282
11283
11284
11285
11286
11287
11288
11289
11290
11291
11292
11293
11294
11295
11296
11297
11298
11299
11300
11301
11302
11303
11304
11305
11306
11307
11308
11309
11310
11311
11312
11313
11314
11315
11316
11317
11318
11319
11320
11321
11322
11323
11324
11325
11326
11327
11328
11329
11330
11331
11332
11333
11334
11335
11336
11337
11338
11339
11340
11341
11342
11343
11344
11345
11346
11347
11348
11349
11350
11351
11352
11353
11354
11355
11356
11357
11358
11359
11360
11361
11362
11363
11364
11365
11366
11367
11368
11369
11370
11371
11372
11373
11374
11375
11376
11377
11378
11379
11380
11381
11382
11383
11384
11385
11386
11387
11388
11389
11390
11391
11392
11393
11394
11395
11396
11397
11398
11399
11400
11401
11402
11403
11404
11405
11406
11407
11408
11409
11410
11411
11412
11413
11414
11415
11416
11417
11418
11419
11420
11421
11422
11423
11424
11425
11426
11427
11428
11429
11430
11431
11432
11433
11434
11435
11436
11437
11438
11439
11440
11441
11442
11443
11444
11445
11446
11447
11448
11449
11450
11451
11452
11453
11454
11455
11456
11457
11458
11459
11460
11461
11462
11463
11464
11465
11466
11467
11468
11469
11470
11471
11472
11473
11474
11475
11476
11477
11478
11479
11480
11481
11482
11483
11484
11485
11486
11487
11488
11489
11490
11491
11492
11493
11494
11495
11496
11497
11498
11499
11500
11501
11502
11503
11504
11505
11506
11507
11508
11509
11510
11511
11512
11513
11514
11515
11516
11517
11518
11519
11520
11521
11522
11523
11524
11525
11526
11527
11528
11529
11530
11531
11532
11533
11534
11535
11536
11537
11538
11539
11540
11541
11542
11543
11544
11545
11546
11547
11548
11549
11550
11551
11552
11553
11554
11555
11556
11557
11558
11559
11560
11561
11562
11563
11564
11565
11566
11567
11568
11569
11570
11571
11572
11573
11574
11575
11576
11577
11578
11579
11580
11581
11582
11583
11584
11585
11586
11587
11588
11589
11590
11591
11592
11593
11594
11595
11596
11597
11598
11599
11600
11601
11602
11603
11604
11605
11606
11607
11608
11609
11610
11611
11612
11613
11614
11615
11616
11617
11618
11619
11620
11621
11622
11623
11624
11625
11626
11627
11628
11629
11630
11631
11632
11633
11634
11635
11636
11637
11638
11639
11640
11641
11642
11643
11644
11645
11646
11647
11648
11649
11650
11651
11652
11653
11654
11655
11656
11657
11658
11659
11660
11661
11662
11663
11664
11665
11666
11667
11668
11669
11670
11671
11672
11673
11674
11675
11676
11677
11678
11679
11680
11681
11682
11683
11684
11685
11686
11687
11688
11689
11690
11691
11692
11693
11694
11695
11696
11697
11698
11699
11700
11701
11702
11703
11704
11705
11706
11707
11708
11709
11710
11711
11712
11713
11714
11715
11716
11717
11718
11719
11720
11721
11722
11723
11724
11725
11726
11727
11728
11729
11730
11731
11732
11733
11734
11735
11736
11737
11738
11739
11740
11741
11742
11743
11744
11745
11746
11747
11748
11749
11750
11751
11752
11753
11754
11755
11756
11757
11758
11759
11760
11761
11762
11763
11764
11765
11766
11767
11768
11769
11770
11771
11772
11773
11774
11775
11776
11777
11778
11779
11780
11781
11782
11783
11784
11785
11786
11787
11788
11789
11790
11791
11792
11793
11794
11795
11796
11797
11798
11799
11800
11801
11802
11803
11804
11805
11806
11807
11808
11809
11810
11811
11812
11813
11814
11815
11816
11817
11818
11819
11820
11821
11822
11823
11824
11825
11826
11827
11828
11829
11830
11831
11832
11833
11834
11835
11836
11837
11838
11839
11840
11841
11842
11843
11844
11845
11846
11847
11848
11849
11850
11851
11852
11853
11854
11855
11856
11857
11858
11859
11860
11861
11862
11863
11864
11865
11866
11867
11868
11869
11870
11871
11872
11873
11874
11875
11876
11877
11878
11879
11880
11881
11882
11883
11884
11885
11886
11887
11888
11889
11890
11891
11892
11893
11894
11895
11896
11897
11898
11899
11900
11901
11902
11903
11904
11905
11906
11907
11908
11909
11910
11911
11912
11913
11914
11915
11916
11917
11918
11919
11920
11921
11922
11923
11924
11925
11926
11927
11928
11929
11930
11931
11932
11933
11934
11935
11936
11937
11938
11939
11940
11941
11942
11943
11944
11945
11946
11947
11948
11949
11950
11951
11952
11953
11954
11955
11956
11957
11958
11959
11960
11961
11962
11963
11964
11965
11966
11967
11968
11969
11970
11971
11972
11973
11974
11975
11976
11977
11978
11979
11980
11981
11982
11983
11984
11985
11986
11987
11988
11989
11990
11991
11992
11993
11994
11995
11996
11997
11998
11999
12000
12001
12002
12003
12004
12005
12006
12007
12008
12009
12010
12011
12012
12013
12014
12015
12016
12017
12018
12019
12020
12021
12022
12023
12024
12025
12026
12027
12028
12029
12030
12031
12032
12033
12034
12035
12036
12037
12038
12039
12040
12041
12042
12043
12044
12045
12046
12047
12048
12049
12050
12051
12052
12053
12054
12055
12056
12057
12058
12059
12060
12061
12062
12063
12064
12065
12066
12067
12068
12069
12070
12071
12072
12073
12074
12075
12076
12077
12078
12079
12080
12081
12082
12083
12084
12085
12086
12087
12088
12089
12090
12091
12092
12093
12094
12095
12096
12097
12098
12099
12100
12101
12102
12103
12104
12105
12106
12107
12108
12109
12110
12111
12112
12113
12114
12115
12116
12117
12118
12119
12120
12121
12122
12123
12124
12125
12126
12127
12128
12129
12130
12131
12132
12133
12134
12135
12136
12137
12138
12139
12140
12141
12142
12143
12144
12145
12146
12147
12148
12149
12150
12151
12152
12153
12154
12155
12156
12157
12158
12159
12160
12161
12162
12163
12164
12165
12166
12167
12168
12169
12170
12171
12172
12173
12174
12175
12176
12177
12178
12179
12180
12181
12182
12183
12184
12185
12186
12187
12188
12189
12190
12191
12192
12193
12194
12195
12196
12197
12198
12199
12200
12201
12202
12203
12204
12205
12206
12207
12208
12209
12210
12211
12212
12213
12214
12215
12216
12217
12218
12219
12220
12221
12222
12223
12224
12225
12226
12227
12228
12229
12230
12231
12232
12233
12234
12235
12236
12237
12238
12239
12240
12241
12242
12243
12244
12245
12246
12247
12248
12249
12250
12251
12252
12253
12254
12255
12256
12257
12258
12259
12260
12261
12262
12263
12264
12265
12266
12267
12268
12269
12270
12271
12272
12273
12274
12275
12276
12277
12278
12279
12280
12281
12282
12283
12284
12285
12286
12287
12288
12289
12290
12291
12292
12293
12294
12295
12296
12297
12298
12299
12300
12301
12302
12303
12304
12305
12306
12307
12308
12309
12310
12311
12312
12313
12314
12315
12316
12317
12318
12319
12320
12321
12322
12323
12324
12325
12326
12327
12328
12329
12330
12331
12332
12333
12334
12335
12336
12337
12338
12339
12340
12341
12342
12343
12344
12345
12346
12347
12348
12349
12350
12351
12352
12353
12354
12355
12356
12357
12358
12359
12360
12361
12362
12363
12364
12365
12366
12367
12368
12369
12370
12371
12372
12373
12374
12375
12376
12377
12378
12379
12380
12381
12382
12383
12384
12385
12386
12387
12388
12389
12390
12391
12392
12393
12394
12395
12396
12397
12398
12399
12400
12401
12402
12403
12404
12405
12406
12407
12408
12409
12410
12411
12412
12413
12414
12415
12416
12417
12418
12419
12420
12421
12422
12423
12424
12425
12426
12427
12428
12429
12430
12431
12432
12433
12434
12435
12436
12437
12438
12439
12440
12441
12442
12443
12444
12445
12446
12447
12448
12449
12450
12451
12452
12453
12454
12455
12456
12457
12458
12459
12460
12461
12462
12463
12464
12465
12466
12467
12468
12469
12470
12471
12472
12473
12474
12475
12476
12477
12478
12479
12480
12481
12482
12483
12484
12485
12486
12487
12488
12489
12490
12491
12492
12493
12494
12495
12496
12497
12498
12499
12500
12501
12502
12503
12504
12505
12506
12507
12508
12509
12510
12511
12512
12513
12514
12515
12516
12517
12518
12519
12520
12521
12522
12523
12524
12525
12526
12527
12528
12529
12530
12531
12532
12533
12534
12535
12536
12537
12538
12539
12540
12541
12542
12543
12544
12545
12546
12547
12548
12549
12550
12551
12552
12553
12554
12555
12556
12557
12558
12559
12560
12561
12562
12563
12564
12565
12566
12567
12568
12569
12570
12571
12572
12573
12574
12575
12576
12577
12578
12579
12580
12581
12582
12583
12584
12585
12586
12587
12588
12589
12590
12591
12592
12593
12594
12595
12596
12597
12598
12599
12600
12601
12602
12603
12604
12605
12606
12607
12608
12609
12610
12611
12612
12613
12614
12615
12616
12617
12618
12619
12620
12621
12622
12623
12624
12625
12626
12627
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nine Nines</title>
    <link>https://ninenines.eu/</link>
    <description>Recent content on Nine Nines</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 23 Dec 2019 07:00:00 +0100</lastBuildDate>
    
	<atom:link href="https://ninenines.eu/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/guide/introduction/</guid>
      <description>Gun is an HTTP client for Erlang/OTP.
Gun supports the HTTP/2, HTTP/1.1 and Websocket protocols.
Prerequisites Knowledge of Erlang, but also of the HTTP/1.1, HTTP/2 and Websocket protocols is required in order to read this guide.
Supported platforms Gun is tested and supported on Linux, FreeBSD, Windows and OSX.
Gun is developed for Erlang/OTP 19.0 and newer.
License Gun uses the ISC License.
Copyright (c) 2013-2018, Loïc Hoguin &amp;lt;[email protected]&amp;gt; Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/guide/introduction/</guid>
      <description>Gun is an HTTP client for Erlang/OTP.
Gun supports the HTTP/2, HTTP/1.1 and Websocket protocols.
Prerequisites Knowledge of Erlang, but also of the HTTP/1.1, HTTP/2 and Websocket protocols is required in order to read this guide.
Supported platforms Gun is tested and supported on Linux, FreeBSD, Windows and OSX.
Gun is developed for Erlang/OTP 19.0 and newer.
License Gun uses the ISC License.
Copyright (c) 2013-2018, Loïc Hoguin &amp;lt;[email protected]&amp;gt; Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/guide/introduction/</guid>
      <description>Gun is an HTTP client for Erlang/OTP.
Gun supports the HTTP/2, HTTP/1.1 and Websocket protocols.
Prerequisites Knowledge of Erlang, but also of the HTTP/1.1, HTTP/2 and Websocket protocols is required in order to read this guide.
Supported platforms Gun is tested and supported on Linux, FreeBSD, Windows and OSX.
Gun is developed for Erlang/OTP 19.0 and newer.
License Gun uses the ISC License.
Copyright (c) 2013-2018, Loïc Hoguin &amp;lt;[email protected]&amp;gt; Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/guide/introduction/</guid>
      <description>Gun is an HTTP client for Erlang/OTP.
Gun supports the HTTP/2, HTTP/1.1 and Websocket protocols.
Prerequisites Knowledge of Erlang, but also of the HTTP/1.1, HTTP/2 and Websocket protocols is required in order to read this guide.
Supported platforms Gun is tested and supported on Linux, FreeBSD, Windows and OSX.
Gun is developed for Erlang/OTP 19.0 and newer.
License Gun uses the ISC License.
Copyright (c) 2013-2018, Loïc Hoguin &amp;lt;[email protected]&amp;gt; Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/guide/introduction/</guid>
      <description>Gun is an HTTP client for Erlang/OTP.
Gun supports the HTTP/2, HTTP/1.1 and Websocket protocols.
Prerequisites Knowledge of Erlang, but also of the HTTP/1.1, HTTP/2 and Websocket protocols is required in order to read this guide.
Supported platforms Gun is tested and supported on Linux, FreeBSD, Windows and OSX.
Gun is developed for Erlang/OTP 20.0 and newer.
Note that Gun will not work on the Windows build of Erlang/OTP 20.3 due to a bug in Erlang/OTP&amp;apos;s stdlib application.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/guide/introduction/</guid>
      <description>Ranch is a socket acceptor pool for TCP protocols.
Ranch aims to provide everything you need to accept TCP connections with a small code base and low latency while being easy to use directly as an application or to embed into your own.
Prerequisites It is assumed the developer already knows Erlang and has some experience with socket programming and TCP protocols.
Supported platforms Ranch is tested and supported on Linux, FreeBSD, OSX and Windows.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/guide/introduction/</guid>
      <description>Ranch is a socket acceptor pool for TCP protocols.
Ranch aims to provide everything you need to accept TCP connections with a small code base and low latency while being easy to use directly as an application or to embed into your own.
Prerequisites It is assumed the developer already knows Erlang and has some experience with socket programming and TCP protocols.
Supported platforms Ranch is tested and supported on Linux, FreeBSD, OSX and Windows.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/guide/introduction/</guid>
      <description>Ranch is a socket acceptor pool for TCP protocols.
Ranch aims to provide everything you need to accept TCP connections with a small code base and low latency while being easy to use directly as an application or to embed into your own.
Prerequisites It is assumed the developer already knows Erlang and has some experience with socket programming and TCP protocols.
Supported platforms Ranch is tested and supported on Linux, FreeBSD, OSX and Windows.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/introduction/</guid>
      <description>Ranch is a socket acceptor pool for TCP protocols.
Ranch aims to provide everything you need to accept TCP connections with a small code base and low latency while being easy to use directly as an application or to embed into your own.
Prerequisites It is assumed the developer already knows Erlang and has some experience with socket programming and TCP protocols.
Supported platforms Ranch is tested and supported on Linux, FreeBSD, OSX and Windows.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/introduction/</guid>
      <description>Ranch is a socket acceptor pool for TCP protocols.
Ranch aims to provide everything you need to accept TCP connections with a small code base and low latency while being easy to use directly as an application or to embed into your own.
Prerequisites It is assumed the developer already knows Erlang and has some experience with socket programming and TCP protocols.
Supported platforms Ranch is tested and supported on Linux, FreeBSD, macOS and Windows.</description>
    </item>
    
    <item>
      <title>The modern Web</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/modern_web/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/modern_web/</guid>
      <description>Cowboy is a server for the modern Web. This chapter explains what it means and details all the standards involved.
Cowboy supports all the standards listed in this document.
HTTP/2 HTTP/2 is the most efficient protocol for consuming Web services. It enables clients to keep a connection open for long periods of time; to send requests concurrently; to reduce the size of requests through HTTP headers compression; and more. The protocol is binary, greatly reducing the resources needed to parse it.</description>
    </item>
    
    <item>
      <title>The modern Web</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/modern_web/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/modern_web/</guid>
      <description>Cowboy is a server for the modern Web. This chapter explains what it means and details all the standards involved.
Cowboy supports all the standards listed in this document.
HTTP/2 HTTP/2 is the most efficient protocol for consuming Web services. It enables clients to keep a connection open for long periods of time; to send requests concurrently; to reduce the size of requests through HTTP headers compression; and more. The protocol is binary, greatly reducing the resources needed to parse it.</description>
    </item>
    
    <item>
      <title>The modern Web</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/modern_web/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/modern_web/</guid>
      <description>Cowboy is a server for the modern Web. This chapter explains what it means and details all the standards involved.
Cowboy supports all the standards listed in this document.
HTTP/2 HTTP/2 is the most efficient protocol for consuming Web services. It enables clients to keep a connection open for long periods of time; to send requests concurrently; to reduce the size of requests through HTTP headers compression; and more. The protocol is binary, greatly reducing the resources needed to parse it.</description>
    </item>
    
    <item>
      <title>The modern Web</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/modern_web/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/modern_web/</guid>
      <description>Cowboy is a server for the modern Web. This chapter explains what it means and details all the standards involved.
Cowboy supports all the standards listed in this document.
HTTP/2 HTTP/2 is the most efficient protocol for consuming Web services. It enables clients to keep a connection open for long periods of time; to send requests concurrently; to reduce the size of requests through HTTP headers compression; and more. The protocol is binary, greatly reducing the resources needed to parse it.</description>
    </item>
    
    <item>
      <title>The modern Web</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/modern_web/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/modern_web/</guid>
      <description>Cowboy is a server for the modern Web. This chapter explains what it means and details all the standards involved.
Cowboy supports all the standards listed in this document.
HTTP/2 HTTP/2 is the most efficient protocol for consuming Web services. It enables clients to keep a connection open for long periods of time; to send requests concurrently; to reduce the size of requests through HTTP headers compression; and more. The protocol is binary, greatly reducing the resources needed to parse it.</description>
    </item>
    
    <item>
      <title>The modern Web</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/modern_web/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/modern_web/</guid>
      <description>Cowboy is a server for the modern Web. This chapter explains what it means and details all the standards involved.
Cowboy supports all the standards listed in this document.
HTTP/2 HTTP/2 is the most efficient protocol for consuming Web services. It enables clients to keep a connection open for long periods of time; to send requests concurrently; to reduce the size of requests through HTTP headers compression; and more. The protocol is binary, greatly reducing the resources needed to parse it.</description>
    </item>
    
    <item>
      <title>Erlang and the Web</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/erlang_web/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/erlang_web/</guid>
      <description>Erlang is the ideal platform for writing Web applications. Its features are a perfect match for the requirements of modern Web applications.
The Web is concurrent When you access a website there is little concurrency involved. A few connections are opened and requests are sent through these connections. Then the web page is displayed on your screen. Your browser will only open up to 4 or 8 connections to the server, depending on your settings.</description>
    </item>
    
    <item>
      <title>Erlang and the Web</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/erlang_web/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/erlang_web/</guid>
      <description>Erlang is the ideal platform for writing Web applications. Its features are a perfect match for the requirements of modern Web applications.
The Web is concurrent When you access a website there is little concurrency involved. A few connections are opened and requests are sent through these connections. Then the web page is displayed on your screen. Your browser will only open up to 4 or 8 connections to the server, depending on your settings.</description>
    </item>
    
    <item>
      <title>Erlang and the Web</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/erlang_web/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/erlang_web/</guid>
      <description>Erlang is the ideal platform for writing Web applications. Its features are a perfect match for the requirements of modern Web applications.
The Web is concurrent When you access a website there is little concurrency involved. A few connections are opened and requests are sent through these connections. Then the web page is displayed on your screen. Your browser will only open up to 4 or 8 connections to the server, depending on your settings.</description>
    </item>
    
    <item>
      <title>Erlang and the Web</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/erlang_web/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/erlang_web/</guid>
      <description>Erlang is the ideal platform for writing Web applications. Its features are a perfect match for the requirements of modern Web applications.
The Web is concurrent When you access a website there is little concurrency involved. A few connections are opened and requests are sent through these connections. Then the web page is displayed on your screen. Your browser will only open up to 4 or 8 connections to the server, depending on your settings.</description>
    </item>
    
    <item>
      <title>Erlang and the Web</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/erlang_web/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/erlang_web/</guid>
      <description>Erlang is the ideal platform for writing Web applications. Its features are a perfect match for the requirements of modern Web applications.
The Web is concurrent When you access a website there is little concurrency involved. A few connections are opened and requests are sent through these connections. Then the web page is displayed on your screen. Your browser will only open up to 4 or 8 connections to the server, depending on your settings.</description>
    </item>
    
    <item>
      <title>Erlang and the Web</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/erlang_web/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/erlang_web/</guid>
      <description>Erlang is the ideal platform for writing Web applications. Its features are a perfect match for the requirements of modern Web applications.
The Web is concurrent When you access a website there is little concurrency involved. A few connections are opened and requests are sent through these connections. Then the web page is displayed on your screen. Your browser will only open up to 4 or 8 connections to the server, depending on your settings.</description>
    </item>
    
    <item>
      <title>Listeners</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/guide/listeners/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/guide/listeners/</guid>
      <description>A listener is a set of processes whose role is to listen on a port for new connections. It manages a pool of acceptor processes, each of them indefinitely accepting connections. When it does, it starts a new process executing the protocol handler code. All the socket programming is abstracted through the use of transport handlers.
The listener takes care of supervising all the acceptor and connection processes, allowing developers to focus on building their application.</description>
    </item>
    
    <item>
      <title>Listeners</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/guide/listeners/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/guide/listeners/</guid>
      <description>A listener is a set of processes whose role is to listen on a port for new connections. It manages a pool of acceptor processes, each of them indefinitely accepting connections. When it does, it starts a new process executing the protocol handler code. All the socket programming is abstracted through the use of transport handlers.
The listener takes care of supervising all the acceptor and connection processes, allowing developers to focus on building their application.</description>
    </item>
    
    <item>
      <title>Listeners</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/guide/listeners/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/guide/listeners/</guid>
      <description>A listener is a set of processes whose role is to listen on a port for new connections. It manages a pool of acceptor processes, each of them indefinitely accepting connections. When it does, it starts a new process executing the protocol handler code. All the socket programming is abstracted through the use of transport handlers.
The listener takes care of supervising all the acceptor and connection processes, allowing developers to focus on building their application.</description>
    </item>
    
    <item>
      <title>Listeners</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/listeners/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/listeners/</guid>
      <description>A listener is a set of processes whose role is to listen on a port for new connections. It manages a pool of acceptor processes, each of them indefinitely accepting connections. When it does, it starts a new process executing the protocol handler code. All the socket programming is abstracted through the use of transport handlers.
The listener takes care of supervising all the acceptor and connection processes, allowing developers to focus on building their application.</description>
    </item>
    
    <item>
      <title>Listeners</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/listeners/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/listeners/</guid>
      <description>A listener is a set of processes whose role is to listen on a port for new connections. It manages a pool of acceptor processes, each of them indefinitely accepting connections. When it does, it starts a new process executing the protocol handler code. All the socket programming is abstracted through the use of transport handlers.
The listener takes care of supervising all the acceptor and connection processes, allowing developers to focus on building their application.</description>
    </item>
    
    <item>
      <title>Starting and stopping</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/guide/start/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/guide/start/</guid>
      <description>This chapter describes how to start and stop the Gun application.
Setting up Specify Gun as a dependency to your application in your favorite build tool.
With Erlang.mk this is done by adding gun to the DEPS variable in your Makefile.
Adding Gun as an Erlang.mk dependency source-highlight: could not find a language definition for make  Starting Gun is an OTP application. It needs to be started before you can use it.</description>
    </item>
    
    <item>
      <title>Starting and stopping</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/guide/start/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/guide/start/</guid>
      <description>This chapter describes how to start and stop the Gun application.
Setting up Specify Gun as a dependency to your application in your favorite build tool.
With Erlang.mk this is done by adding gun to the DEPS variable in your Makefile.
Adding Gun as an Erlang.mk dependency source-highlight: could not find a language definition for make  Starting Gun is an OTP application. It needs to be started before you can use it.</description>
    </item>
    
    <item>
      <title>Starting and stopping</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/guide/start/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/guide/start/</guid>
      <description>This chapter describes how to start and stop the Gun application.
Setting up Specify Gun as a dependency to your application in your favorite build tool.
With Erlang.mk this is done by adding gun to the DEPS variable in your Makefile.
Adding Gun as an Erlang.mk dependency source-highlight: could not find a language definition for make  Starting Gun is an OTP application. It needs to be started before you can use it.</description>
    </item>
    
    <item>
      <title>Starting and stopping</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/guide/start/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/guide/start/</guid>
      <description>This chapter describes how to start and stop the Gun application.
Setting up Specify Gun as a dependency to your application in your favorite build tool.
With Erlang.mk this is done by adding gun to the DEPS variable in your Makefile.
Adding Gun as an Erlang.mk dependency source-highlight: could not find a language definition for make  Starting Gun is an OTP application. It needs to be started before you can use it.</description>
    </item>
    
    <item>
      <title>Starting and stopping</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/guide/start/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/guide/start/</guid>
      <description>This chapter describes how to start and stop the Gun application.
Setting up Specify Gun as a dependency to your application in your favorite build tool.
With Erlang.mk this is done by adding gun to the DEPS variable in your Makefile.
Adding Gun as an Erlang.mk dependency source-highlight: could not find a language definition for make  Starting Gun is an OTP application. It needs to be started before you can use it.</description>
    </item>
    
    <item>
      <title>Supported protocols</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/guide/protocols/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/guide/protocols/</guid>
      <description>This chapter describes the protocols supported and the operations available to them.
HTTP/1.1 HTTP/1.1 is a text request-response protocol. The client sends a request, the server sends back a response.
Gun provides convenience functions for performing GET, HEAD, OPTIONS, POST, PATCH, PUT, and DELETE requests. All these functions are aliases of gun:request/4,5,6 for the respective methods. Gun also provides a gun:data/4 function for streaming the request body.
Gun will send a gun_inform message for every intermediate informational responses received.</description>
    </item>
    
    <item>
      <title>Supported protocols</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/guide/protocols/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/guide/protocols/</guid>
      <description>This chapter describes the protocols supported and the operations available to them.
HTTP/1.1 HTTP/1.1 is a text request-response protocol. The client sends a request, the server sends back a response.
Gun provides convenience functions for performing GET, HEAD, OPTIONS, POST, PATCH, PUT, and DELETE requests. All these functions are aliases of gun:request/4,5,6 for the respective methods. Gun also provides a gun:data/4 function for streaming the request body.
Gun will send a gun_inform message for every intermediate informational responses received.</description>
    </item>
    
    <item>
      <title>Supported protocols</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/guide/protocols/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/guide/protocols/</guid>
      <description>This chapter describes the protocols supported and the operations available to them.
HTTP/1.1 HTTP/1.1 is a text request-response protocol. The client sends a request, the server sends back a response.
Gun provides convenience functions for performing GET, HEAD, OPTIONS, POST, PATCH, PUT, and DELETE requests. All these functions are aliases of gun:request/4,5,6 for the respective methods. Gun also provides a gun:data/4 function for streaming the request body.
Gun will send a gun_inform message for every intermediate informational responses received.</description>
    </item>
    
    <item>
      <title>Supported protocols</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/guide/protocols/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/guide/protocols/</guid>
      <description>This chapter describes the protocols supported and the operations available to them.
HTTP/1.1 HTTP/1.1 is a text request-response protocol. The client sends a request, the server sends back a response.
Gun provides convenience functions for performing GET, HEAD, OPTIONS, POST, PATCH, PUT, and DELETE requests. All these functions are aliases of gun:request/4,5,6 for the respective methods. Gun also provides a gun:data/4 function for streaming the request body.
Gun will send a gun_inform message for every intermediate informational responses received.</description>
    </item>
    
    <item>
      <title>Supported protocols</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/guide/protocols/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/guide/protocols/</guid>
      <description>This chapter describes the protocols supported and the operations available to them.
HTTP/1.1 HTTP/1.1 is a text request-response protocol. The client sends a request, the server sends back a response.
Gun provides convenience functions for performing GET, HEAD, OPTIONS, POST, PATCH, PUT, and DELETE requests. All these functions are aliases of gun:headers/4,5 or gun:request/5,6 for the respective methods. Gun also provides a gun:data/4 function for streaming the request body.
Gun will send a gun_inform message for every intermediate informational responses received.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/introduction/</guid>
      <description>Cowboy is a small, fast and modern HTTP server for Erlang/OTP.
Cowboy aims to provide a complete modern Web stack. This includes HTTP/1.1, HTTP/2, Websocket, Server-Sent Events and Webmachine-based REST.
Cowboy comes with functions for introspection and tracing, enabling developers to know precisely what is happening at any time. Its modular design also easily enable developers to add instrumentation.
Cowboy is a high quality project. It has a small code base, is very efficient (both in latency and memory use) and can easily be embedded in another application.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/introduction/</guid>
      <description>Cowboy is a small, fast and modern HTTP server for Erlang/OTP.
Cowboy aims to provide a complete modern Web stack. This includes HTTP/1.1, HTTP/2, Websocket, Server-Sent Events and Webmachine-based REST.
Cowboy comes with functions for introspection and tracing, enabling developers to know precisely what is happening at any time. Its modular design also easily enable developers to add instrumentation.
Cowboy is a high quality project. It has a small code base, is very efficient (both in latency and memory use) and can easily be embedded in another application.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/introduction/</guid>
      <description>Cowboy is a small, fast and modern HTTP server for Erlang/OTP.
Cowboy aims to provide a complete modern Web stack. This includes HTTP/1.1, HTTP/2, Websocket, Server-Sent Events and Webmachine-based REST.
Cowboy comes with functions for introspection and tracing, enabling developers to know precisely what is happening at any time. Its modular design also easily enable developers to add instrumentation.
Cowboy is a high quality project. It has a small code base, is very efficient (both in latency and memory use) and can easily be embedded in another application.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/introduction/</guid>
      <description>Cowboy is a small, fast and modern HTTP server for Erlang/OTP.
Cowboy aims to provide a complete modern Web stack. This includes HTTP/1.1, HTTP/2, Websocket, Server-Sent Events and Webmachine-based REST.
Cowboy comes with functions for introspection and tracing, enabling developers to know precisely what is happening at any time. Its modular design also easily enable developers to add instrumentation.
Cowboy is a high quality project. It has a small code base, is very efficient (both in latency and memory use) and can easily be embedded in another application.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/introduction/</guid>
      <description>Cowboy is a small, fast and modern HTTP server for Erlang/OTP.
Cowboy aims to provide a complete modern Web stack. This includes HTTP/1.1, HTTP/2, Websocket, Server-Sent Events and Webmachine-based REST.
Cowboy comes with functions for introspection and tracing, enabling developers to know precisely what is happening at any time. Its modular design also easily enable developers to add instrumentation.
Cowboy is a high quality project. It has a small code base, is very efficient (both in latency and memory use) and can easily be embedded in another application.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/introduction/</guid>
      <description>Cowboy is a small, fast and modern HTTP server for Erlang/OTP.
Cowboy aims to provide a complete modern Web stack. This includes HTTP/1.1, HTTP/2, Websocket, Server-Sent Events and Webmachine-based REST.
Cowboy comes with functions for introspection and tracing, enabling developers to know precisely what is happening at any time. Its modular design also easily enable developers to add instrumentation.
Cowboy is a high quality project. It has a small code base, is very efficient (both in latency and memory use) and can easily be embedded in another application.</description>
    </item>
    
    <item>
      <title>Transports</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/guide/transports/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/guide/transports/</guid>
      <description>A transport defines the interface to interact with a socket.
Transports can be used for connecting, listening and accepting connections, but also for receiving and sending data. Both passive and active mode are supported, although all sockets are initialized as passive.
TCP transport The TCP transport is a thin wrapper around gen_tcp.
SSL transport The SSL transport is a thin wrapper around ssl.
Ranch depends on ssl by default so any necessary dependencies will start when Ranch is started.</description>
    </item>
    
    <item>
      <title>Transports</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/guide/transports/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/guide/transports/</guid>
      <description>A transport defines the interface to interact with a socket.
Transports can be used for connecting, listening and accepting connections, but also for receiving and sending data. Both passive and active mode are supported, although all sockets are initialized as passive.
TCP transport The TCP transport is a thin wrapper around gen_tcp.
SSL transport The SSL transport is a thin wrapper around ssl.
Ranch depends on ssl by default so any necessary dependencies will start when Ranch is started.</description>
    </item>
    
    <item>
      <title>Transports</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/guide/transports/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/guide/transports/</guid>
      <description>A transport defines the interface to interact with a socket.
Transports can be used for connecting, listening and accepting connections, but also for receiving and sending data. Both passive and active mode are supported, although all sockets are initialized as passive.
TCP transport The TCP transport is a thin wrapper around gen_tcp.
SSL transport The SSL transport is a thin wrapper around ssl.
Ranch depends on ssl by default so any necessary dependencies will start when Ranch is started.</description>
    </item>
    
    <item>
      <title>Transports</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/transports/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/transports/</guid>
      <description>A transport defines the interface to interact with a socket.
Transports can be used for connecting, listening and accepting connections, but also for receiving and sending data. Both passive and active mode are supported, although all sockets are initialized as passive.
TCP transport The TCP transport is a thin wrapper around gen_tcp.
SSL transport The SSL transport is a thin wrapper around ssl.
Ranch depends on ssl by default so any necessary dependencies will start when Ranch is started.</description>
    </item>
    
    <item>
      <title>Transports</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/transports/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/transports/</guid>
      <description>A transport defines the interface to interact with a socket.
Transports can be used for connecting, listening and accepting connections, but also for receiving and sending data. Both passive and active mode are supported, although all sockets are initialized as passive.
TCP transport The TCP transport is a thin wrapper around gen_tcp.
SSL transport The SSL transport is a thin wrapper around ssl.
Ranch depends on ssl by default so any necessary dependencies will start when Ranch is started.</description>
    </item>
    
    <item>
      <title>Connection</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/guide/connect/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/guide/connect/</guid>
      <description>This chapter describes how to open, monitor and close a connection using the Gun client.
Gun connections Gun is designed with the HTTP/2 and Websocket protocols in mind. They are built for long-running connections that allow concurrent exchange of data, either in the form of request/responses for HTTP/2 or in the form of messages for Websocket.
A Gun connection is an Erlang process that manages a socket to a remote endpoint.</description>
    </item>
    
    <item>
      <title>Connection</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/guide/connect/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/guide/connect/</guid>
      <description>This chapter describes how to open, monitor and close a connection using the Gun client.
Gun connections Gun is designed with the HTTP/2 and Websocket protocols in mind. They are built for long-running connections that allow concurrent exchange of data, either in the form of request/responses for HTTP/2 or in the form of messages for Websocket.
A Gun connection is an Erlang process that manages a socket to a remote endpoint.</description>
    </item>
    
    <item>
      <title>Connection</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/guide/connect/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/guide/connect/</guid>
      <description>This chapter describes how to open, monitor and close a connection using the Gun client.
Gun connections Gun is designed with the HTTP/2 and Websocket protocols in mind. They are built for long-running connections that allow concurrent exchange of data, either in the form of request/responses for HTTP/2 or in the form of messages for Websocket.
A Gun connection is an Erlang process that manages a socket to a remote endpoint.</description>
    </item>
    
    <item>
      <title>Connection</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/guide/connect/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/guide/connect/</guid>
      <description>This chapter describes how to open, monitor and close a connection using the Gun client.
Gun connections Gun is designed with the HTTP/2 and Websocket protocols in mind. They are built for long-running connections that allow concurrent exchange of data, either in the form of request/responses for HTTP/2 or in the form of messages for Websocket.
A Gun connection is an Erlang process that manages a socket to a remote endpoint.</description>
    </item>
    
    <item>
      <title>Connection</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/guide/connect/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/guide/connect/</guid>
      <description>This chapter describes how to open, monitor and close a connection using the Gun client.
Gun connections Gun is designed with the HTTP/2 and Websocket protocols in mind. They are built for long-running connections that allow concurrent exchange of data, either in the form of request/responses for HTTP/2 or in the form of messages for Websocket.
A Gun connection is an Erlang process that manages a socket to a remote endpoint.</description>
    </item>
    
    <item>
      <title>Protocols</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/guide/protocols/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/guide/protocols/</guid>
      <description>A protocol handler starts a connection process and defines the protocol logic executed in this process.
Writing a protocol handler All protocol handlers must implement the ranch_protocol behavior which defines a single callback, start_link/4. This callback is responsible for spawning a new process for handling the connection. It receives four arguments: the name of the listener, the socket, the transport handler being used and the protocol options defined in the call to ranch:start_listener/5.</description>
    </item>
    
    <item>
      <title>Protocols</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/guide/protocols/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/guide/protocols/</guid>
      <description>A protocol handler starts a connection process and defines the protocol logic executed in this process.
Writing a protocol handler All protocol handlers must implement the ranch_protocol behavior which defines a single callback, start_link/4. This callback is responsible for spawning a new process for handling the connection. It receives four arguments: the name of the listener, the socket, the transport handler being used and the protocol options defined in the call to ranch:start_listener/5.</description>
    </item>
    
    <item>
      <title>Protocols</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/guide/protocols/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/guide/protocols/</guid>
      <description>A protocol handler starts a connection process and defines the protocol logic executed in this process.
Writing a protocol handler All protocol handlers must implement the ranch_protocol behavior which defines a single callback, start_link/4. This callback is responsible for spawning a new process for handling the connection. It receives four arguments: the name of the listener, the socket, the transport handler being used and the protocol options defined in the call to ranch:start_listener/5.</description>
    </item>
    
    <item>
      <title>Protocols</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/protocols/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/protocols/</guid>
      <description>A protocol handler starts a connection process and defines the protocol logic executed in this process.
Writing a protocol handler All protocol handlers must implement the ranch_protocol behavior which defines a single callback, start_link/4. This callback is responsible for spawning a new process for handling the connection. It receives four arguments: the name of the listener, the socket, the transport handler being used and the protocol options defined in the call to ranch:start_listener/5.</description>
    </item>
    
    <item>
      <title>Protocols</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/protocols/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/protocols/</guid>
      <description>A protocol handler starts a connection process and defines the protocol logic executed in this process.
Writing a protocol handler All protocol handlers must implement the ranch_protocol behavior which defines a single callback, start_link/3. This callback is responsible for spawning a new process for handling the connection. It receives four arguments: the name of the listener, the socket, the transport handler being used and the protocol options defined in the call to ranch:start_listener/5.</description>
    </item>
    
    <item>
      <title>Getting started</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/getting_started/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/getting_started/</guid>
      <description>Erlang is more than a language, it is also an operating system for your applications. Erlang developers rarely write standalone modules, they write libraries or applications, and then bundle those into what is called a release. A release contains the Erlang VM plus all applications required to run the node, so it can be pushed to production directly.
This chapter walks you through all the steps of setting up Cowboy, writing your first application and generating your first release.</description>
    </item>
    
    <item>
      <title>Getting started</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/getting_started/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/getting_started/</guid>
      <description>Erlang is more than a language, it is also an operating system for your applications. Erlang developers rarely write standalone modules, they write libraries or applications, and then bundle those into what is called a release. A release contains the Erlang VM plus all applications required to run the node, so it can be pushed to production directly.
This chapter walks you through all the steps of setting up Cowboy, writing your first application and generating your first release.</description>
    </item>
    
    <item>
      <title>Getting started</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/getting_started/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/getting_started/</guid>
      <description>Erlang is more than a language, it is also an operating system for your applications. Erlang developers rarely write standalone modules, they write libraries or applications, and then bundle those into what is called a release. A release contains the Erlang VM plus all applications required to run the node, so it can be pushed to production directly.
This chapter walks you through all the steps of setting up Cowboy, writing your first application and generating your first release.</description>
    </item>
    
    <item>
      <title>Getting started</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/getting_started/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/getting_started/</guid>
      <description>Erlang is more than a language, it is also an operating system for your applications. Erlang developers rarely write standalone modules, they write libraries or applications, and then bundle those into what is called a release. A release contains the Erlang VM plus all applications required to run the node, so it can be pushed to production directly.
This chapter walks you through all the steps of setting up Cowboy, writing your first application and generating your first release.</description>
    </item>
    
    <item>
      <title>Getting started</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/getting_started/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/getting_started/</guid>
      <description>Erlang is more than a language, it is also an operating system for your applications. Erlang developers rarely write standalone modules, they write libraries or applications, and then bundle those into what is called a release. A release contains the Erlang VM plus all applications required to run the node, so it can be pushed to production directly.
This chapter walks you through all the steps of setting up Cowboy, writing your first application and generating your first release.</description>
    </item>
    
    <item>
      <title>Getting started</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/getting_started/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/getting_started/</guid>
      <description>Erlang is more than a language, it is also an operating system for your applications. Erlang developers rarely write standalone modules, they write libraries or applications, and then bundle those into what is called a release. A release contains the Erlang VM plus all applications required to run the node, so it can be pushed to production directly.
This chapter walks you through all the steps of setting up Cowboy, writing your first application and generating your first release.</description>
    </item>
    
    <item>
      <title>HTTP</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/guide/http/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/guide/http/</guid>
      <description>This chapter describes how to use the Gun client for communicating with an HTTP/1.1 or HTTP/2 server.
Streams Every time a request is initiated, Gun creates a stream. A stream reference uniquely identifies a set of request and response and must be used to perform additional operations with a stream or to identify its messages.
Stream references use the Erlang reference data type and are therefore unique.
Streams can be canceled at any time.</description>
    </item>
    
    <item>
      <title>HTTP</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/guide/http/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/guide/http/</guid>
      <description>This chapter describes how to use the Gun client for communicating with an HTTP/1.1 or HTTP/2 server.
Streams Every time a request is initiated, Gun creates a stream. A stream reference uniquely identifies a set of request and response and must be used to perform additional operations with a stream or to identify its messages.
Stream references use the Erlang reference data type and are therefore unique.
Streams can be canceled at any time.</description>
    </item>
    
    <item>
      <title>HTTP</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/guide/http/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/guide/http/</guid>
      <description>This chapter describes how to use the Gun client for communicating with an HTTP/1.1 or HTTP/2 server.
Streams Every time a request is initiated, Gun creates a stream. A stream reference uniquely identifies a set of request and response and must be used to perform additional operations with a stream or to identify its messages.
Stream references use the Erlang reference data type and are therefore unique.
Streams can be canceled at any time.</description>
    </item>
    
    <item>
      <title>HTTP</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/guide/http/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/guide/http/</guid>
      <description>This chapter describes how to use the Gun client for communicating with an HTTP/1.1 or HTTP/2 server.
Streams Every time a request is initiated, Gun creates a stream. A stream reference uniquely identifies a set of request and response and must be used to perform additional operations with a stream or to identify its messages.
Stream references use the Erlang reference data type and are therefore unique.
Streams can be canceled at any time.</description>
    </item>
    
    <item>
      <title>HTTP</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/guide/http/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/guide/http/</guid>
      <description>This chapter describes how to use the Gun client for communicating with an HTTP/1.1 or HTTP/2 server.
Streams Every time a request is initiated, Gun creates a stream. A stream reference uniquely identifies a set of request and response and must be used to perform additional operations with a stream or to identify its messages.
Stream references use the Erlang reference data type and are therefore unique.
Streams can be canceled at any time.</description>
    </item>
    
    <item>
      <title>Embedded mode</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/guide/embedded/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/guide/embedded/</guid>
      <description>Embedded mode allows you to insert Ranch listeners directly in your supervision tree. This allows for greater fault tolerance control by permitting the shutdown of a listener due to the failure of another part of the application and vice versa.
Embedding To embed Ranch in your application you can simply add the child specs to your supervision tree. This can all be done in the init/1 function of one of your application supervisors.</description>
    </item>
    
    <item>
      <title>Embedded mode</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/guide/embedded/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/guide/embedded/</guid>
      <description>Embedded mode allows you to insert Ranch listeners directly in your supervision tree. This allows for greater fault tolerance control by permitting the shutdown of a listener due to the failure of another part of the application and vice versa.
Embedding To embed Ranch in your application you can simply add the child specs to your supervision tree. This can all be done in the init/1 function of one of your application supervisors.</description>
    </item>
    
    <item>
      <title>Embedded mode</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/guide/embedded/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/guide/embedded/</guid>
      <description>Embedded mode allows you to insert Ranch listeners directly in your supervision tree. This allows for greater fault tolerance control by permitting the shutdown of a listener due to the failure of another part of the application and vice versa.
Embedding To embed Ranch in your application you can simply add the child specs to your supervision tree. This can all be done in the init/1 function of one of your application supervisors.</description>
    </item>
    
    <item>
      <title>Embedded mode</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/embedded/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/embedded/</guid>
      <description>Embedded mode allows you to insert Ranch listeners directly in your supervision tree. This allows for greater fault tolerance control by permitting the shutdown of a listener due to the failure of another part of the application and vice versa.
Embedding To embed Ranch in your application you can simply add the child specs to your supervision tree. This can all be done in the init/1 function of one of your application supervisors.</description>
    </item>
    
    <item>
      <title>Embedded mode</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/embedded/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/embedded/</guid>
      <description>Embedded mode allows you to insert Ranch listeners directly in your supervision tree. This allows for greater fault tolerance control by permitting the shutdown of a listener due to the failure of another part of the application and vice versa.
However, just as for non-embedded listeners that were started via ranch:start_listener/5, it is required that the ranch application is running before you can start embedded listeners. Furthermore, this also means that embedded listeners will restart when ranch_sup fails.</description>
    </item>
    
    <item>
      <title>Flow diagram</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/flow_diagram/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/flow_diagram/</guid>
      <description>Cowboy is a lightweight HTTP server with support for HTTP/1.1, HTTP/2 and Websocket.
It is built on top of Ranch. Please see the Ranch guide for more information about how the network connections are handled.
Overview As you can see on the diagram, the client begins by connecting to the server. This step is handled by a Ranch acceptor, which is a process dedicated to accepting new connections.
After Ranch accepts a new connection, whether it is an HTTP/1.</description>
    </item>
    
    <item>
      <title>Flow diagram</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/flow_diagram/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/flow_diagram/</guid>
      <description>Cowboy is a lightweight HTTP server with support for HTTP/1.1, HTTP/2 and Websocket.
It is built on top of Ranch. Please see the Ranch guide for more information about how the network connections are handled.
Overview As you can see on the diagram, the client begins by connecting to the server. This step is handled by a Ranch acceptor, which is a process dedicated to accepting new connections.
After Ranch accepts a new connection, whether it is an HTTP/1.</description>
    </item>
    
    <item>
      <title>Flow diagram</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/flow_diagram/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/flow_diagram/</guid>
      <description>Cowboy is a lightweight HTTP server with support for HTTP/1.1, HTTP/2 and Websocket.
It is built on top of Ranch. Please see the Ranch guide for more information about how the network connections are handled.
Overview As you can see on the diagram, the client begins by connecting to the server. This step is handled by a Ranch acceptor, which is a process dedicated to accepting new connections.
After Ranch accepts a new connection, whether it is an HTTP/1.</description>
    </item>
    
    <item>
      <title>Flow diagram</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/flow_diagram/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/flow_diagram/</guid>
      <description>Cowboy is a lightweight HTTP server with support for HTTP/1.1, HTTP/2 and Websocket.
It is built on top of Ranch. Please see the Ranch guide for more information about how the network connections are handled.
Overview As you can see on the diagram, the client begins by connecting to the server. This step is handled by a Ranch acceptor, which is a process dedicated to accepting new connections.
After Ranch accepts a new connection, whether it is an HTTP/1.</description>
    </item>
    
    <item>
      <title>Flow diagram</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/flow_diagram/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/flow_diagram/</guid>
      <description>Cowboy is a lightweight HTTP server with support for HTTP/1.1, HTTP/2 and Websocket.
It is built on top of Ranch. Please see the Ranch guide for more information about how the network connections are handled.
Overview As you can see on the diagram, the client begins by connecting to the server. This step is handled by a Ranch acceptor, which is a process dedicated to accepting new connections.
After Ranch accepts a new connection, whether it is an HTTP/1.</description>
    </item>
    
    <item>
      <title>Flow diagram</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/flow_diagram/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/flow_diagram/</guid>
      <description>Cowboy is a lightweight HTTP server with support for HTTP/1.1, HTTP/2 and Websocket.
It is built on top of Ranch. Please see the Ranch guide for more information about how the network connections are handled.
Overview As you can see on the diagram, the client begins by connecting to the server. This step is handled by a Ranch acceptor, which is a process dedicated to accepting new connections.
After Ranch accepts a new connection, whether it is an HTTP/1.</description>
    </item>
    
    <item>
      <title>Websocket</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/guide/websocket/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/guide/websocket/</guid>
      <description>This chapter describes how to use the Gun client for communicating with a Websocket server.
HTTP upgrade Websocket is a protocol built on top of HTTP. To use Websocket, you must first request for the connection to be upgraded. Only HTTP/1.1 connections can be upgraded to Websocket, so you might need to restrict the protocol to HTTP/1.1 if you are planning to use Websocket over TLS.
You must use the gun:ws_upgrade/2,3,4 function to upgrade to Websocket.</description>
    </item>
    
    <item>
      <title>Websocket</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/guide/websocket/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/guide/websocket/</guid>
      <description>This chapter describes how to use the Gun client for communicating with a Websocket server.
HTTP upgrade Websocket is a protocol built on top of HTTP. To use Websocket, you must first request for the connection to be upgraded. Only HTTP/1.1 connections can be upgraded to Websocket, so you might need to restrict the protocol to HTTP/1.1 if you are planning to use Websocket over TLS.
You must use the gun:ws_upgrade/2,3,4 function to upgrade to Websocket.</description>
    </item>
    
    <item>
      <title>Websocket</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/guide/websocket/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/guide/websocket/</guid>
      <description>This chapter describes how to use the Gun client for communicating with a Websocket server.
HTTP upgrade Websocket is a protocol built on top of HTTP. To use Websocket, you must first request for the connection to be upgraded. Only HTTP/1.1 connections can be upgraded to Websocket, so you might need to restrict the protocol to HTTP/1.1 if you are planning to use Websocket over TLS.
You must use the gun:ws_upgrade/2,3,4 function to upgrade to Websocket.</description>
    </item>
    
    <item>
      <title>Websocket</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/guide/websocket/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/guide/websocket/</guid>
      <description>This chapter describes how to use the Gun client for communicating with a Websocket server.
HTTP upgrade Websocket is a protocol built on top of HTTP. To use Websocket, you must first request for the connection to be upgraded. Only HTTP/1.1 connections can be upgraded to Websocket, so you might need to restrict the protocol to HTTP/1.1 if you are planning to use Websocket over TLS.
You must use the gun:ws_upgrade/2,3,4 function to upgrade to Websocket.</description>
    </item>
    
    <item>
      <title>Websocket</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/guide/websocket/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/guide/websocket/</guid>
      <description>This chapter describes how to use the Gun client for communicating with a Websocket server.
HTTP upgrade Websocket is a protocol built on top of HTTP. To use Websocket, you must first request for the connection to be upgraded. Only HTTP/1.1 connections can be upgraded to Websocket, so you might need to restrict the protocol to HTTP/1.1 if you are planning to use Websocket over TLS.
You must use the gun:ws_upgrade/2,3,4 function to upgrade to Websocket.</description>
    </item>
    
    <item>
      <title>Writing parsers</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/guide/parsers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/guide/parsers/</guid>
      <description>There are three kinds of protocols:
Text protocols  Schema-less binary protocols  Schema-based binary protocols   This chapter introduces the first two kinds. It will not cover more advanced topics such as continuations or parser generators.
This chapter isn&amp;apos;t specifically about Ranch, we assume here that you know how to read data from the socket. The data you read and the data that hasn&amp;apos;t been parsed is saved in a buffer.</description>
    </item>
    
    <item>
      <title>Writing parsers</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/guide/parsers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/guide/parsers/</guid>
      <description>There are three kinds of protocols:
Text protocols  Schema-less binary protocols  Schema-based binary protocols   This chapter introduces the first two kinds. It will not cover more advanced topics such as continuations or parser generators.
This chapter isn&amp;apos;t specifically about Ranch, we assume here that you know how to read data from the socket. The data you read and the data that hasn&amp;apos;t been parsed is saved in a buffer.</description>
    </item>
    
    <item>
      <title>Writing parsers</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/guide/parsers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/guide/parsers/</guid>
      <description>There are three kinds of protocols:
Text protocols  Schema-less binary protocols  Schema-based binary protocols   This chapter introduces the first two kinds. It will not cover more advanced topics such as continuations or parser generators.
This chapter isn&amp;apos;t specifically about Ranch, we assume here that you know how to read data from the socket. The data you read and the data that hasn&amp;apos;t been parsed is saved in a buffer.</description>
    </item>
    
    <item>
      <title>Writing parsers</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/parsers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/parsers/</guid>
      <description>There are three kinds of protocols:
Text protocols  Schema-less binary protocols  Schema-based binary protocols   This chapter introduces the first two kinds. It will not cover more advanced topics such as continuations or parser generators.
This chapter isn&amp;apos;t specifically about Ranch, we assume here that you know how to read data from the socket. The data you read and the data that hasn&amp;apos;t been parsed is saved in a buffer.</description>
    </item>
    
    <item>
      <title>Writing parsers</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/parsers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/parsers/</guid>
      <description>There are three kinds of protocols:
Text protocols  Schema-less binary protocols  Schema-based binary protocols   This chapter introduces the first two kinds. It will not cover more advanced topics such as continuations or parser generators.
This chapter isn&amp;apos;t specifically about Ranch, we assume here that you know how to read data from the socket. The data you read and the data that hasn&amp;apos;t been parsed is saved in a buffer.</description>
    </item>
    
    <item>
      <title>Changes since Gun 1.3</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/guide/migrating_from_1.3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/guide/migrating_from_1.3/</guid>
      <description>The following patch versions were released since Gun 1.3:
Gun 1.3.1 This release backports a fix that will be included in the upcoming Gun 2.0 release:
POTENTIAL SECURITY VULNERABILITY: Fix transfer-encoding precedence over content-length in responses. This bug may contribute to a response smuggling security vulnerability when Gun is used inside a proxy.   </description>
    </item>
    
    <item>
      <title>Migrating from Gun 1.0 to 1.1</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/guide/migrating_from_1.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/guide/migrating_from_1.0/</guid>
      <description>Gun 1.1 updates the Cowlib dependency to 2.5.1 and fixes a few problems with experimental features.
Features added Update Cowlib to 2.5.1   Bugs fixed A bug in the experimental gun_sse_h where lone id lines were not propagated has been fixed by updating the Cowlib dependency.  The status code was incorrectly given to the experimental content handlers as a binary. It has been fixed an an integer is now given as was intended.</description>
    </item>
    
    <item>
      <title>Migrating from Gun 1.1 to 1.2</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/guide/migrating_from_1.1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/guide/migrating_from_1.1/</guid>
      <description>Gun 1.2 adds support for the CONNECT request over HTTP/1.1 connections.
Features added CONNECT requests can now be issued on HTTP/1.1 connections. The tunneled connection can use any of the protocols Gun supports: HTTP/1.1, HTTP/2 and Websocket over both TCP and TLS transports. Note that Gun currently does not support tunneling a TLS connection over a TLS connection due to limitations in Erlang/OTP.  Gun supports sending multiple CONNECT requests, allowing the tunnel to the origin server to go through multiple proxies.</description>
    </item>
    
    <item>
      <title>Migrating from Gun 1.3 to 2.0</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/guide/migrating_from_1.3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/guide/migrating_from_1.3/</guid>
      <description>Gun 2.0 adds many features including graceful shutdown, flow control for data messages, event handlers, support for tunneling TLS connections through TLS proxies, Socks proxy support, and much more. It has only a limited number of breaking changes compared to the previous version.
Gun 2.0 greatly improves the HTTP/2 performance when it comes to receiving large response bodies; and when receiving response bodies from many separate requests concurrently.
Gun now shares much of its HTTP/2 code with Cowboy, including the HTTP/2 state machine.</description>
    </item>
    
    <item>
      <title>Listeners</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/listeners/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/listeners/</guid>
      <description>A listener is a set of processes that listens on a port for new connections. Incoming connections get handled by Cowboy. Depending on the connection handshake, one or another protocol may be used.
This chapter is specific to Cowboy. Please refer to the Ranch User Guide for more information about listeners.
Cowboy provides two types of listeners: one listening for clear TCP connections, and one listening for secure TLS connections. Both of them support the HTTP/1.</description>
    </item>
    
    <item>
      <title>Listeners</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/listeners/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/listeners/</guid>
      <description>A listener is a set of processes that listens on a port for new connections. Incoming connections get handled by Cowboy. Depending on the connection handshake, one or another protocol may be used.
This chapter is specific to Cowboy. Please refer to the Ranch User Guide for more information about listeners.
Cowboy provides two types of listeners: one listening for clear TCP connections, and one listening for secure TLS connections. Both of them support the HTTP/1.</description>
    </item>
    
    <item>
      <title>Listeners</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/listeners/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/listeners/</guid>
      <description>A listener is a set of processes that listens on a port for new connections. Incoming connections get handled by Cowboy. Depending on the connection handshake, one or another protocol may be used.
This chapter is specific to Cowboy. Please refer to the Ranch User Guide for more information about listeners.
Cowboy provides two types of listeners: one listening for clear TCP connections, and one listening for secure TLS connections. Both of them support the HTTP/1.</description>
    </item>
    
    <item>
      <title>Listeners</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/listeners/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/listeners/</guid>
      <description>A listener is a set of processes that listens on a port for new connections. Incoming connections get handled by Cowboy. Depending on the connection handshake, one or another protocol may be used.
This chapter is specific to Cowboy. Please refer to the Ranch User Guide for more information about listeners.
Cowboy provides two types of listeners: one listening for clear TCP connections, and one listening for secure TLS connections. Both of them support the HTTP/1.</description>
    </item>
    
    <item>
      <title>Listeners</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/listeners/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/listeners/</guid>
      <description>A listener is a set of processes that listens on a port for new connections. Incoming connections get handled by Cowboy. Depending on the connection handshake, one or another protocol may be used.
This chapter is specific to Cowboy. Please refer to the Ranch User Guide for more information about listeners.
Cowboy provides two types of listeners: one listening for clear TCP connections, and one listening for secure TLS connections. Both of them support the HTTP/1.</description>
    </item>
    
    <item>
      <title>Listeners</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/listeners/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/listeners/</guid>
      <description>A listener is a set of processes that listens on a port for new connections. Incoming connections get handled by Cowboy. Depending on the connection handshake, one or another protocol may be used.
This chapter is specific to Cowboy. Please refer to the Ranch User Guide for more information about listeners.
Cowboy provides two types of listeners: one listening for clear TCP connections, and one listening for secure TLS connections. Both of them support the HTTP/1.</description>
    </item>
    
    <item>
      <title>SSL client authentication</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/guide/ssl_auth/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/guide/ssl_auth/</guid>
      <description>Purpose SSL client authentication is a mechanism allowing applications to identify certificates. This allows your application to make sure that the client is an authorized certificate, but makes no claim about whether the user can be trusted. This can be combined with a password based authentication to attain greater security.
The server only needs to retain the certificate serial number and the certificate issuer to authenticate the certificate. Together, they can be used to uniquely identify a certicate.</description>
    </item>
    
    <item>
      <title>SSL client authentication</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/guide/ssl_auth/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/guide/ssl_auth/</guid>
      <description>Purpose SSL client authentication is a mechanism allowing applications to identify certificates. This allows your application to make sure that the client is an authorized certificate, but makes no claim about whether the user can be trusted. This can be combined with a password based authentication to attain greater security.
The server only needs to retain the certificate serial number and the certificate issuer to authenticate the certificate. Together, they can be used to uniquely identify a certicate.</description>
    </item>
    
    <item>
      <title>SSL client authentication</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/guide/ssl_auth/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/guide/ssl_auth/</guid>
      <description>Purpose SSL client authentication is a mechanism allowing applications to identify certificates. This allows your application to make sure that the client is an authorized certificate, but makes no claim about whether the user can be trusted. This can be combined with a password based authentication to attain greater security.
The server only needs to retain the certificate serial number and the certificate issuer to authenticate the certificate. Together, they can be used to uniquely identify a certicate.</description>
    </item>
    
    <item>
      <title>SSL client authentication</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/ssl_auth/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/ssl_auth/</guid>
      <description>Purpose SSL client authentication is a mechanism allowing applications to identify certificates. This allows your application to make sure that the client is an authorized certificate, but makes no claim about whether the user can be trusted. This can be combined with a password based authentication to attain greater security.
The server only needs to retain the certificate serial number and the certificate issuer to authenticate the certificate. Together, they can be used to uniquely identify a certicate.</description>
    </item>
    
    <item>
      <title>SSL client authentication</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/ssl_auth/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/ssl_auth/</guid>
      <description>Purpose SSL client authentication is a mechanism allowing applications to identify certificates. This allows your application to make sure that the client is an authorized certificate, but makes no claim about whether the user can be trusted. This can be combined with a password based authentication to attain greater security.
The server only needs to retain the certificate serial number and the certificate issuer to authenticate the certificate. Together, they can be used to uniquely identify a certicate.</description>
    </item>
    
    <item>
      <title>Routing</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/routing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/routing/</guid>
      <description>Cowboy does nothing by default.
To make Cowboy useful, you need to map URIs to Erlang modules that will handle the requests. This is called routing.
When Cowboy receives a request, it tries to match the requested host and path to the configured routes. When there&amp;apos;s a match, the route&amp;apos;s associated handler is executed.
Routes need to be compiled before they can be used by Cowboy. The result of the compilation is the dispatch rules.</description>
    </item>
    
    <item>
      <title>Routing</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/routing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/routing/</guid>
      <description>Cowboy does nothing by default.
To make Cowboy useful, you need to map URIs to Erlang modules that will handle the requests. This is called routing.
When Cowboy receives a request, it tries to match the requested host and path to the configured routes. When there&amp;apos;s a match, the route&amp;apos;s associated handler is executed.
Routes need to be compiled before they can be used by Cowboy. The result of the compilation is the dispatch rules.</description>
    </item>
    
    <item>
      <title>Routing</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/routing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/routing/</guid>
      <description>Cowboy does nothing by default.
To make Cowboy useful, you need to map URIs to Erlang modules that will handle the requests. This is called routing.
When Cowboy receives a request, it tries to match the requested host and path to the configured routes. When there&amp;apos;s a match, the route&amp;apos;s associated handler is executed.
Routes need to be compiled before they can be used by Cowboy. The result of the compilation is the dispatch rules.</description>
    </item>
    
    <item>
      <title>Routing</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/routing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/routing/</guid>
      <description>Cowboy does nothing by default.
To make Cowboy useful, you need to map URIs to Erlang modules that will handle the requests. This is called routing.
When Cowboy receives a request, it tries to match the requested host and path to the configured routes. When there&amp;apos;s a match, the route&amp;apos;s associated handler is executed.
Routes need to be compiled before they can be used by Cowboy. The result of the compilation is the dispatch rules.</description>
    </item>
    
    <item>
      <title>Routing</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/routing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/routing/</guid>
      <description>Cowboy does nothing by default.
To make Cowboy useful, you need to map URIs to Erlang modules that will handle the requests. This is called routing.
When Cowboy receives a request, it tries to match the requested host and path to the configured routes. When there&amp;apos;s a match, the route&amp;apos;s associated handler is executed.
Routes need to be compiled before they can be used by Cowboy. The result of the compilation is the dispatch rules.</description>
    </item>
    
    <item>
      <title>Routing</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/routing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/routing/</guid>
      <description>Cowboy does nothing by default.
To make Cowboy useful, you need to map URIs to Erlang modules that will handle the requests. This is called routing.
When Cowboy receives a request, it tries to match the requested host and path to the configured routes. When there&amp;apos;s a match, the route&amp;apos;s associated handler is executed.
Routes need to be compiled before they can be used by Cowboy. The result of the compilation is the dispatch rules.</description>
    </item>
    
    <item>
      <title>Connection draining</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/connection_draining/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/connection_draining/</guid>
      <description>Stopping a Ranch listener via ranch:stop_listener/1 will invariably kill all connection processes the listener hosts. However, you may want to stop a listener in a graceful fashion, ie by not accepting any new connections, but allowing the existing connection processes to exit by themselves instead of being killed.
For this purpose, you should first suspend the listener you wish to stop gracefully, and then wait for its connection count to drop to zero.</description>
    </item>
    
    <item>
      <title>Internals</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/guide/internals/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/guide/internals/</guid>
      <description>This chapter may not apply to embedded Ranch as embedding allows you to use an architecture specific to your application, which may or may not be compatible with the description of the Ranch application.
Note that for everything related to efficiency and performance, you should perform the benchmarks yourself to get the numbers that matter to you. Generic benchmarks found on the web may or may not be of use to you, you can never know until you benchmark your own system.</description>
    </item>
    
    <item>
      <title>Internals</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/guide/internals/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/guide/internals/</guid>
      <description>This chapter may not apply to embedded Ranch as embedding allows you to use an architecture specific to your application, which may or may not be compatible with the description of the Ranch application.
Note that for everything related to efficiency and performance, you should perform the benchmarks yourself to get the numbers that matter to you. Generic benchmarks found on the web may or may not be of use to you, you can never know until you benchmark your own system.</description>
    </item>
    
    <item>
      <title>Internals</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/guide/internals/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/guide/internals/</guid>
      <description>This chapter may not apply to embedded Ranch as embedding allows you to use an architecture specific to your application, which may or may not be compatible with the description of the Ranch application.
Note that for everything related to efficiency and performance, you should perform the benchmarks yourself to get the numbers that matter to you. Generic benchmarks found on the web may or may not be of use to you, you can never know until you benchmark your own system.</description>
    </item>
    
    <item>
      <title>Internals</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/internals/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/internals/</guid>
      <description>This chapter may not apply to embedded Ranch as embedding allows you to use an architecture specific to your application, which may or may not be compatible with the description of the Ranch application.
Note that for everything related to efficiency and performance, you should perform the benchmarks yourself to get the numbers that matter to you. Generic benchmarks found on the web may or may not be of use to you, you can never know until you benchmark your own system.</description>
    </item>
    
    <item>
      <title>Migrating from Gun 1.0 to 1.1</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/guide/migrating_from_1.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/guide/migrating_from_1.0/</guid>
      <description>Gun 1.1 updates the Cowlib dependency to 2.5.1 and fixes a few problems with experimental features.
Features added Update Cowlib to 2.5.1   Bugs fixed A bug in the experimental gun_sse_h where lone id lines were not propagated has been fixed by updating the Cowlib dependency.  The status code was incorrectly given to the experimental content handlers as a binary. It has been fixed an an integer is now given as was intended.</description>
    </item>
    
    <item>
      <title>Migrating from Gun 1.2 to 1.3</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/guide/migrating_from_1.2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/guide/migrating_from_1.2/</guid>
      <description>Gun 1.3 improves the support for CONNECT requests introduced in the previous version and documents Websocket protocol negotiation.
Features added The protocols CONNECT destination option has been added as a replacement for the now deprecated protocol option.  Add built-in support for Websocket protocol negotiation through the Websocket option protocols. The interface of the handler module currently remains undocumented and must be set to gun_ws_h.  Add the h2specd HTTP/2 test suite from the h2spec project.</description>
    </item>
    
    <item>
      <title>Migrating from Gun 1.2 to 1.3</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/guide/migrating_from_1.2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/guide/migrating_from_1.2/</guid>
      <description>Gun 1.3 improves the support for CONNECT requests introduced in the previous version and documents Websocket protocol negotiation.
Features added The protocols CONNECT destination option has been added as a replacement for the now deprecated protocol option.  Add built-in support for Websocket protocol negotiation through the Websocket option protocols. The interface of the handler module currently remains undocumented and must be set to gun_ws_h.  Add the h2specd HTTP/2 test suite from the h2spec project.</description>
    </item>
    
    <item>
      <title>Constraints</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/constraints/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/constraints/</guid>
      <description>Constraints are validation and conversion functions applied to user input.
They are used in various places in Cowboy, including the router and the cowboy_req match functions.
Syntax Constraints are provided as a list of fields. For each field in the list, specific constraints can be applied, as well as a default value if the field is missing.
A field can take the form of an atom field, a tuple with constraints {field, Constraints} or a tuple with constraints and a default value {field, Constraints, Default}.</description>
    </item>
    
    <item>
      <title>Constraints</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/constraints/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/constraints/</guid>
      <description>Constraints are validation and conversion functions applied to user input.
They are used in various places in Cowboy, including the router and the cowboy_req match functions.
Syntax Constraints are provided as a list of fields. For each field in the list, specific constraints can be applied, as well as a default value if the field is missing.
A field can take the form of an atom field, a tuple with constraints {field, Constraints} or a tuple with constraints and a default value {field, Constraints, Default}.</description>
    </item>
    
    <item>
      <title>Constraints</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/constraints/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/constraints/</guid>
      <description>Constraints are validation and conversion functions applied to user input.
They are used in various places in Cowboy, including the router and the cowboy_req match functions.
Syntax Constraints are provided as a list of fields. For each field in the list, specific constraints can be applied, as well as a default value if the field is missing.
A field can take the form of an atom field, a tuple with constraints {field, Constraints} or a tuple with constraints and a default value {field, Constraints, Default}.</description>
    </item>
    
    <item>
      <title>Constraints</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/constraints/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/constraints/</guid>
      <description>Constraints are validation and conversion functions applied to user input.
They are used in various places in Cowboy, including the router and the cowboy_req match functions.
Syntax Constraints are provided as a list of fields. For each field in the list, specific constraints can be applied, as well as a default value if the field is missing.
A field can take the form of an atom field, a tuple with constraints {field, Constraints} or a tuple with constraints and a default value {field, Constraints, Default}.</description>
    </item>
    
    <item>
      <title>Constraints</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/constraints/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/constraints/</guid>
      <description>Constraints are validation and conversion functions applied to user input.
They are used in various places in Cowboy, including the router and the cowboy_req match functions.
Syntax Constraints are provided as a list of fields. For each field in the list, specific constraints can be applied, as well as a default value if the field is missing.
A field can take the form of an atom field, a tuple with constraints {field, Constraints} or a tuple with constraints and a default value {field, Constraints, Default}.</description>
    </item>
    
    <item>
      <title>Constraints</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/constraints/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/constraints/</guid>
      <description>Constraints are validation and conversion functions applied to user input.
They are used in various places in Cowboy, including the router and the cowboy_req match functions.
Syntax Constraints are provided as a list of fields. For each field in the list, specific constraints can be applied, as well as a default value if the field is missing.
A field can take the form of an atom field, a tuple with constraints {field, Constraints} or a tuple with constraints and a default value {field, Constraints, Default}.</description>
    </item>
    
    <item>
      <title>Upcoming changes in Ranch 2.0</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/guide/upcoming_2.0_changes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/guide/upcoming_2.0_changes/</guid>
      <description>The following changes will be done in Ranch 2.0. In most cases an alternative is already available in the most recent Ranch version.
The function ranch:start_listener/6 has been deprecated in favor of ranch:start_listener/5. The number of acceptors was removed and will be taken from the transport options.  The function ranch:child_spec/6 has also been deprecated, in favor of ranch:child_spec/5.  The function ranch:accept_ack/1 has been deprecated in favor of ranch:handshake/1,2.  The function ranch:info/1,2 will return a map containing each listener&amp;apos;s information rather than a list of key/values.</description>
    </item>
    
    <item>
      <title>Upcoming changes in Ranch 2.0</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/upcoming_2.0_changes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/upcoming_2.0_changes/</guid>
      <description>The following changes will be done in Ranch 2.0. In most cases an alternative is already available in the most recent Ranch version.
The function ranch:start_listener/6 has been deprecated in favor of ranch:start_listener/5. The number of acceptors was removed and will be taken from the transport options.  The function ranch:child_spec/6 has also been deprecated, in favor of ranch:child_spec/5.  The function ranch:accept_ack/1 has been deprecated in favor of ranch:handshake/1,2.  The function ranch:info/1,2 will return a map containing each listener&amp;apos;s information rather than a list of key/values.</description>
    </item>
    
    <item>
      <title>Internals</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/internals/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/internals/</guid>
      <description>This chapter may not apply to embedded Ranch as embedding allows you to use an architecture specific to your application, which may or may not be compatible with the description of the Ranch application.
Note that for everything related to efficiency and performance, you should perform the benchmarks yourself to get the numbers that matter to you. Generic benchmarks found on the web may or may not be of use to you, you can never know until you benchmark your own system.</description>
    </item>
    
    <item>
      <title>Migrating from Gun 1.1 to 1.2</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/guide/migrating_from_1.1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/guide/migrating_from_1.1/</guid>
      <description>Gun 1.2 adds support for the CONNECT request over HTTP/1.1 connections.
Features added CONNECT requests can now be issued on HTTP/1.1 connections. The tunneled connection can use any of the protocols Gun supports: HTTP/1.1, HTTP/2 and Websocket over both TCP and TLS transports. Note that Gun currently does not support tunneling a TLS connection over a TLS connection due to limitations in Erlang/OTP.  Gun supports sending multiple CONNECT requests, allowing the tunnel to the origin server to go through multiple proxies.</description>
    </item>
    
    <item>
      <title>Migrating from Gun 1.1 to 1.2</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/guide/migrating_from_1.1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/guide/migrating_from_1.1/</guid>
      <description>Gun 1.2 adds support for the CONNECT request over HTTP/1.1 connections.
Features added CONNECT requests can now be issued on HTTP/1.1 connections. The tunneled connection can use any of the protocols Gun supports: HTTP/1.1, HTTP/2 and Websocket over both TCP and TLS transports. Note that Gun currently does not support tunneling a TLS connection over a TLS connection due to limitations in Erlang/OTP.  Gun supports sending multiple CONNECT requests, allowing the tunnel to the origin server to go through multiple proxies.</description>
    </item>
    
    <item>
      <title>Handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/handlers/</guid>
      <description>Handlers are Erlang modules that handle HTTP requests.
Plain HTTP handlers The most basic handler in Cowboy implements the mandatory init/2 callback, manipulates the request, optionally sends a response and then returns.
This callback receives the Req object and the initial state defined in the router configuration.
A handler that does nothing would look like this:
init(Req, State) -&amp;gt; {ok, Req, State}.  Despite sending no reply, a 204 No Content response will be sent to the client, as Cowboy makes sure that a response is sent for every request.</description>
    </item>
    
    <item>
      <title>Handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/handlers/</guid>
      <description>Handlers are Erlang modules that handle HTTP requests.
Plain HTTP handlers The most basic handler in Cowboy implements the mandatory init/2 callback, manipulates the request, optionally sends a response and then returns.
This callback receives the Req object and the initial state defined in the router configuration.
A handler that does nothing would look like this:
init(Req, State) -&amp;gt; {ok, Req, State}.  Despite sending no reply, a 204 No Content response will be sent to the client, as Cowboy makes sure that a response is sent for every request.</description>
    </item>
    
    <item>
      <title>Handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/handlers/</guid>
      <description>Handlers are Erlang modules that handle HTTP requests.
Plain HTTP handlers The most basic handler in Cowboy implements the mandatory init/2 callback, manipulates the request, optionally sends a response and then returns.
This callback receives the Req object and the initial state defined in the router configuration.
A handler that does nothing would look like this:
init(Req, State) -&amp;gt; {ok, Req, State}.  Despite sending no reply, a 204 No Content response will be sent to the client, as Cowboy makes sure that a response is sent for every request.</description>
    </item>
    
    <item>
      <title>Handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/handlers/</guid>
      <description>Handlers are Erlang modules that handle HTTP requests.
Plain HTTP handlers The most basic handler in Cowboy implements the mandatory init/2 callback, manipulates the request, optionally sends a response and then returns.
This callback receives the Req object and the initial state defined in the router configuration.
A handler that does nothing would look like this:
init(Req, State) -&amp;gt; {ok, Req, State}.  Despite sending no reply, a 204 No Content response will be sent to the client, as Cowboy makes sure that a response is sent for every request.</description>
    </item>
    
    <item>
      <title>Handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/handlers/</guid>
      <description>Handlers are Erlang modules that handle HTTP requests.
Plain HTTP handlers The most basic handler in Cowboy implements the mandatory init/2 callback, manipulates the request, optionally sends a response and then returns.
This callback receives the Req object and the initial state defined in the router configuration.
A handler that does nothing would look like this:
init(Req, State) -&amp;gt; {ok, Req, State}.  Despite sending no reply, a 204 No Content response will be sent to the client, as Cowboy makes sure that a response is sent for every request.</description>
    </item>
    
    <item>
      <title>Handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/handlers/</guid>
      <description>Handlers are Erlang modules that handle HTTP requests.
Plain HTTP handlers The most basic handler in Cowboy implements the mandatory init/2 callback, manipulates the request, optionally sends a response and then returns.
This callback receives the Req object and the initial state defined in the router configuration.
A handler that does nothing would look like this:
init(Req, State) -&amp;gt; {ok, Req, State}.  Despite sending no reply, a 204 No Content response will be sent to the client, as Cowboy makes sure that a response is sent for every request.</description>
    </item>
    
    <item>
      <title>Migrating from Ranch 1.7 to Ranch 2.0</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/migrating_from_1.7/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/migrating_from_1.7/</guid>
      <description>Ranch 2.0 adds support for multiple connection supervisors.
Ranch 1.x had a bottleneck because it used only a single connection supervisor. This was more evident when many connections were dropped at once as the supervisor couldn&amp;apos;t keep up and failed to accept new connections while cleaning up the old ones. Ranch 2.0 behaves much better in this scenario by default. Multiple connection supervisors also helps with concurrently accepting new connections.</description>
    </item>
    
    <item>
      <title>Changes since Ranch 1.6</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/guide/migrating_from_1.6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/guide/migrating_from_1.6/</guid>
      <description>The following patch versions were released since Ranch 1.6:
Ranch 1.6.2 This release fixes an issue where listener information would not get cleaned up when an embedded listener was stopped.
Ranch 1.6.1 This release fixes a minor issue in the README and adds an undocumented function to help Cowboy deal with the transition from list to map for the transport options.</description>
    </item>
    
    <item>
      <title>Changes since Ranch 1.7</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/migrating_from_1.7/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/migrating_from_1.7/</guid>
      <description>The following patch versions were released since Ranch 1.7:
Ranch 1.7.1 This release fixes an issue with the PROXY protocol where the wrong CRC32 algorithm was used and would cause checksum verification to fail.
Because the plain crc32 checksum is not supported by the PROXY protocol, the configuration value when building PROXY headers has been changed to crc32c.</description>
    </item>
    
    <item>
      <title>Loop handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/loop_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/loop_handlers/</guid>
      <description>Loop handlers are a special kind of HTTP handlers used when the response can not be sent right away. The handler enters instead a receive loop waiting for the right message before it can send a response.
Loop handlers are used for requests where a response might not be immediately available, but where you would like to keep the connection open for a while in case the response arrives. The most known example of such practice is known as long polling.</description>
    </item>
    
    <item>
      <title>Loop handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/loop_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/loop_handlers/</guid>
      <description>Loop handlers are a special kind of HTTP handlers used when the response can not be sent right away. The handler enters instead a receive loop waiting for the right message before it can send a response.
Loop handlers are used for requests where a response might not be immediately available, but where you would like to keep the connection open for a while in case the response arrives. The most known example of such practice is known as long polling.</description>
    </item>
    
    <item>
      <title>Loop handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/loop_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/loop_handlers/</guid>
      <description>Loop handlers are a special kind of HTTP handlers used when the response can not be sent right away. The handler enters instead a receive loop waiting for the right message before it can send a response.
Loop handlers are used for requests where a response might not be immediately available, but where you would like to keep the connection open for a while in case the response arrives. The most known example of such practice is known as long polling.</description>
    </item>
    
    <item>
      <title>Loop handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/loop_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/loop_handlers/</guid>
      <description>Loop handlers are a special kind of HTTP handlers used when the response can not be sent right away. The handler enters instead a receive loop waiting for the right message before it can send a response.
Loop handlers are used for requests where a response might not be immediately available, but where you would like to keep the connection open for a while in case the response arrives. The most known example of such practice is known as long polling.</description>
    </item>
    
    <item>
      <title>Loop handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/loop_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/loop_handlers/</guid>
      <description>Loop handlers are a special kind of HTTP handlers used when the response can not be sent right away. The handler enters instead a receive loop waiting for the right message before it can send a response.
Loop handlers are used for requests where a response might not be immediately available, but where you would like to keep the connection open for a while in case the response arrives. The most known example of such practice is known as long polling.</description>
    </item>
    
    <item>
      <title>Loop handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/loop_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/loop_handlers/</guid>
      <description>Loop handlers are a special kind of HTTP handlers used when the response can not be sent right away. The handler enters instead a receive loop waiting for the right message before it can send a response.
Loop handlers are used for requests where a response might not be immediately available, but where you would like to keep the connection open for a while in case the response arrives. The most known example of such practice is known as long polling.</description>
    </item>
    
    <item>
      <title>Migrating from Gun 1.0 to 1.1</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/guide/migrating_from_1.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/guide/migrating_from_1.0/</guid>
      <description>Gun 1.1 updates the Cowlib dependency to 2.5.1 and fixes a few problems with experimental features.
Features added Update Cowlib to 2.5.1   Bugs fixed A bug in the experimental gun_sse_h where lone id lines were not propagated has been fixed by updating the Cowlib dependency.  The status code was incorrectly given to the experimental content handlers as a binary. It has been fixed an an integer is now given as was intended.</description>
    </item>
    
    <item>
      <title>Migrating from Gun 1.0 to 1.1</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/guide/migrating_from_1.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/guide/migrating_from_1.0/</guid>
      <description>Gun 1.1 updates the Cowlib dependency to 2.5.1 and fixes a few problems with experimental features.
Features added Update Cowlib to 2.5.1   Bugs fixed A bug in the experimental gun_sse_h where lone id lines were not propagated has been fixed by updating the Cowlib dependency.  The status code was incorrectly given to the experimental content handlers as a binary. It has been fixed an an integer is now given as was intended.</description>
    </item>
    
    <item>
      <title>Static files</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/static_files/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/static_files/</guid>
      <description>Cowboy comes with a ready to use handler for serving static files. It is provided as a convenience for serving files during development.
For systems in production, consider using one of the many Content Distribution Network (CDN) available on the market, as they are the best solution for serving files.
The static handler can serve either one file or all files from a given directory. The etag generation and mime types can be configured.</description>
    </item>
    
    <item>
      <title>Static files</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/static_files/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/static_files/</guid>
      <description>Cowboy comes with a ready to use handler for serving static files. It is provided as a convenience for serving files during development.
For systems in production, consider using one of the many Content Distribution Network (CDN) available on the market, as they are the best solution for serving files.
The static handler can serve either one file or all files from a given directory. The etag generation and mime types can be configured.</description>
    </item>
    
    <item>
      <title>Static files</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/static_files/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/static_files/</guid>
      <description>Cowboy comes with a ready to use handler for serving static files. It is provided as a convenience for serving files during development.
For systems in production, consider using one of the many Content Distribution Network (CDN) available on the market, as they are the best solution for serving files.
The static handler can serve either one file or all files from a given directory. The etag generation and mime types can be configured.</description>
    </item>
    
    <item>
      <title>Static files</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/static_files/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/static_files/</guid>
      <description>Cowboy comes with a ready to use handler for serving static files. It is provided as a convenience for serving files during development.
For systems in production, consider using one of the many Content Distribution Network (CDN) available on the market, as they are the best solution for serving files.
The static handler can serve either one file or all files from a given directory. The etag generation and mime types can be configured.</description>
    </item>
    
    <item>
      <title>Static files</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/static_files/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/static_files/</guid>
      <description>Cowboy comes with a ready to use handler for serving static files. It is provided as a convenience for serving files during development.
For systems in production, consider using one of the many Content Distribution Network (CDN) available on the market, as they are the best solution for serving files.
The static handler can serve either one file or all files from a given directory. The etag generation and mime types can be configured.</description>
    </item>
    
    <item>
      <title>Static files</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/static_files/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/static_files/</guid>
      <description>Cowboy comes with a ready to use handler for serving static files. It is provided as a convenience for serving files during development.
For systems in production, consider using one of the many Content Distribution Network (CDN) available on the market, as they are the best solution for serving files.
The static handler can serve either one file or all files from a given directory. The etag generation and mime types can be configured.</description>
    </item>
    
    <item>
      <title>Migrating from Ranch 1.6 to 1.7</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/migrating_from_1.6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/migrating_from_1.6/</guid>
      <description>Ranch 1.7 adds built-in support for the PROXY protocol.
The PROXY protocol is a simple and efficient way for proxies to transmit information about the client.
While a third-party library already existed, it was not entirely compatible with the Ranch interface, in particular when socket active mode was involved. This new implementation fixes that and supports the full protocol with as little overhead as possible compared to normal operations: just one extra function call.</description>
    </item>
    
    <item>
      <title>Migrating from Ranch 1.5 to 1.6</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/guide/migrating_from_1.5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/guide/migrating_from_1.5/</guid>
      <description>Ranch 1.6 added the ability to suspend and resume listeners. It also deprecates a number of features and add interfaces that will be used in Ranch 2.0.
Ranch 1.6 is compatible with Erlang/OTP 18.0 onward. Support for older releases has been removed.
Features added Listeners can now be suspended/resumed without stopping existing connection processes. This effectively closes the listening socket and stops the acceptor processes.  Transport options can now be updated for suspended listeners.</description>
    </item>
    
    <item>
      <title>Migrating from Ranch 1.6 to 1.7</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/migrating_from_1.6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/migrating_from_1.6/</guid>
      <description>Ranch 1.7 adds built-in support for the PROXY protocol.
The PROXY protocol is a simple and efficient way for proxies to transmit information about the client.
While a third-party library already existed, it was not entirely compatible with the Ranch interface, in particular when socket active mode was involved. This new implementation fixes that and supports the full protocol with as little overhead as possible compared to normal operations: just one extra function call.</description>
    </item>
    
    <item>
      <title>The Req object</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/req/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/req/</guid>
      <description>The Req object is a variable used for obtaining information about a request, read its body or send a response.
It is not really an object in the object-oriented sense. It is a simple map that can be directly accessed or used when calling functions from the cowboy_req module.
The Req object is the subject of a few different chapters. In this chapter we will learn about the Req object and look at how to retrieve information about the request.</description>
    </item>
    
    <item>
      <title>The Req object</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/req/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/req/</guid>
      <description>The Req object is a variable used for obtaining information about a request, read its body or send a response.
It is not really an object in the object-oriented sense. It is a simple map that can be directly accessed or used when calling functions from the cowboy_req module.
The Req object is the subject of a few different chapters. In this chapter we will learn about the Req object and look at how to retrieve information about the request.</description>
    </item>
    
    <item>
      <title>The Req object</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/req/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/req/</guid>
      <description>The Req object is a variable used for obtaining information about a request, read its body or send a response.
It is not really an object in the object-oriented sense. It is a simple map that can be directly accessed or used when calling functions from the cowboy_req module.
The Req object is the subject of a few different chapters. In this chapter we will learn about the Req object and look at how to retrieve information about the request.</description>
    </item>
    
    <item>
      <title>The Req object</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/req/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/req/</guid>
      <description>The Req object is a variable used for obtaining information about a request, read its body or send a response.
It is not really an object in the object-oriented sense. It is a simple map that can be directly accessed or used when calling functions from the cowboy_req module.
The Req object is the subject of a few different chapters. In this chapter we will learn about the Req object and look at how to retrieve information about the request.</description>
    </item>
    
    <item>
      <title>The Req object</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/req/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/req/</guid>
      <description>The Req object is a variable used for obtaining information about a request, read its body or send a response.
It is not really an object in the object-oriented sense. It is a simple map that can be directly accessed or used when calling functions from the cowboy_req module.
The Req object is the subject of a few different chapters. In this chapter we will learn about the Req object and look at how to retrieve information about the request.</description>
    </item>
    
    <item>
      <title>The Req object</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/req/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/req/</guid>
      <description>The Req object is a variable used for obtaining information about a request, read its body or send a response.
It is not really an object in the object-oriented sense. It is a simple map that can be directly accessed or used when calling functions from the cowboy_req module.
The Req object is the subject of a few different chapters. In this chapter we will learn about the Req object and look at how to retrieve information about the request.</description>
    </item>
    
    <item>
      <title>Migrating from Ranch 1.5 to 1.6</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/migrating_from_1.5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/migrating_from_1.5/</guid>
      <description>Ranch 1.6 added the ability to suspend and resume listeners. It also deprecates a number of features and add interfaces that will be used in Ranch 2.0.
Ranch 1.6 is compatible with Erlang/OTP 18.0 onward. Support for older releases has been removed.
Features added Listeners can now be suspended/resumed without stopping existing connection processes. This effectively closes the listening socket and stops the acceptor processes.  Transport options can now be updated for suspended listeners.</description>
    </item>
    
    <item>
      <title>Migrating from Ranch 1.5 to 1.6</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/migrating_from_1.5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/migrating_from_1.5/</guid>
      <description>Ranch 1.6 added the ability to suspend and resume listeners. It also deprecates a number of features and add interfaces that will be used in Ranch 2.0.
Ranch 1.6 is compatible with Erlang/OTP 18.0 onward. Support for older releases has been removed.
Features added Listeners can now be suspended/resumed without stopping existing connection processes. This effectively closes the listening socket and stops the acceptor processes.  Transport options can now be updated for suspended listeners.</description>
    </item>
    
    <item>
      <title>Migrating from Ranch 1.x</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/guide/migrating_from_1.x/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/guide/migrating_from_1.x/</guid>
      <description>The changelog for Ranch releases before 1.6 can be found in this section.
1.5.0 Add transport functions getopts/2, getstat/1 and getstat/2  Fix ranch:info/0 and ranch:procs/2 in embedded mode  Prevent ranch_conns_sup from stopping on unexpected messages   1.4.0 Add new transport option num_acceptor  Deprecate ranch:start_listener/6 in favor of start_listener/5  Deprecate ranch:child_spec/6 in favor of child_spec/5   1.3.0 The version numbers 1.3.1 and 1.3.2 were later made to fix small mistakes made during the 1.</description>
    </item>
    
    <item>
      <title>Reading the request body</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/req_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/req_body/</guid>
      <description>The request body can be read using the Req object.
Cowboy will not attempt to read the body until requested. You need to call the body reading functions in order to retrieve it.
Cowboy will not cache the body, it is therefore only possible to read it once.
You are not required to read it, however. If a body is present and was not read, Cowboy will either cancel or skip its download, depending on the protocol.</description>
    </item>
    
    <item>
      <title>Reading the request body</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/req_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/req_body/</guid>
      <description>The request body can be read using the Req object.
Cowboy will not attempt to read the body until requested. You need to call the body reading functions in order to retrieve it.
Cowboy will not cache the body, it is therefore only possible to read it once.
You are not required to read it, however. If a body is present and was not read, Cowboy will either cancel or skip its download, depending on the protocol.</description>
    </item>
    
    <item>
      <title>Reading the request body</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/req_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/req_body/</guid>
      <description>The request body can be read using the Req object.
Cowboy will not attempt to read the body until requested. You need to call the body reading functions in order to retrieve it.
Cowboy will not cache the body, it is therefore only possible to read it once.
You are not required to read it, however. If a body is present and was not read, Cowboy will either cancel or skip its download, depending on the protocol.</description>
    </item>
    
    <item>
      <title>Reading the request body</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/req_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/req_body/</guid>
      <description>The request body can be read using the Req object.
Cowboy will not attempt to read the body until requested. You need to call the body reading functions in order to retrieve it.
Cowboy will not cache the body, it is therefore only possible to read it once.
You are not required to read it, however. If a body is present and was not read, Cowboy will either cancel or skip its download, depending on the protocol.</description>
    </item>
    
    <item>
      <title>Reading the request body</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/req_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/req_body/</guid>
      <description>The request body can be read using the Req object.
Cowboy will not attempt to read the body until requested. You need to call the body reading functions in order to retrieve it.
Cowboy will not cache the body, it is therefore only possible to read it once.
You are not required to read it, however. If a body is present and was not read, Cowboy will either cancel or skip its download, depending on the protocol.</description>
    </item>
    
    <item>
      <title>Reading the request body</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/req_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/req_body/</guid>
      <description>The request body can be read using the Req object.
Cowboy will not attempt to read the body until requested. You need to call the body reading functions in order to retrieve it.
Cowboy will not cache the body, it is therefore only possible to read it once.
You are not required to read it, however. If a body is present and was not read, Cowboy will either cancel or skip its download, depending on the protocol.</description>
    </item>
    
    <item>
      <title>Sending a response</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/resp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/resp/</guid>
      <description>The response must be sent using the Req object.
Cowboy provides two different ways of sending responses: either directly or by streaming the body. Response headers and body may be set in advance. The response is sent as soon as one of the reply or stream reply function is called.
Cowboy also provides a simplified interface for sending files. It can also send only specific parts of a file.
While only one response is allowed for every request, HTTP/2 introduced a mechanism that allows the server to push additional resources related to the response.</description>
    </item>
    
    <item>
      <title>Sending a response</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/resp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/resp/</guid>
      <description>The response must be sent using the Req object.
Cowboy provides two different ways of sending responses: either directly or by streaming the body. Response headers and body may be set in advance. The response is sent as soon as one of the reply or stream reply function is called.
Cowboy also provides a simplified interface for sending files. It can also send only specific parts of a file.
While only one response is allowed for every request, HTTP/2 introduced a mechanism that allows the server to push additional resources related to the response.</description>
    </item>
    
    <item>
      <title>Sending a response</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/resp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/resp/</guid>
      <description>The response must be sent using the Req object.
Cowboy provides two different ways of sending responses: either directly or by streaming the body. Response headers and body may be set in advance. The response is sent as soon as one of the reply or stream reply function is called.
Cowboy also provides a simplified interface for sending files. It can also send only specific parts of a file.
While only one response is allowed for every request, HTTP/2 introduced a mechanism that allows the server to push additional resources related to the response.</description>
    </item>
    
    <item>
      <title>Sending a response</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/resp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/resp/</guid>
      <description>The response must be sent using the Req object.
Cowboy provides two different ways of sending responses: either directly or by streaming the body. Response headers and body may be set in advance. The response is sent as soon as one of the reply or stream reply function is called.
Cowboy also provides a simplified interface for sending files. It can also send only specific parts of a file.
While only one response is allowed for every request, HTTP/2 introduced a mechanism that allows the server to push additional resources related to the response.</description>
    </item>
    
    <item>
      <title>Sending a response</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/resp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/resp/</guid>
      <description>The response must be sent using the Req object.
Cowboy provides two different ways of sending responses: either directly or by streaming the body. Response headers and body may be set in advance. The response is sent as soon as one of the reply or stream reply function is called.
Cowboy also provides a simplified interface for sending files. It can also send only specific parts of a file.
While only one response is allowed for every request, HTTP/2 introduced a mechanism that allows the server to push additional resources related to the response.</description>
    </item>
    
    <item>
      <title>Sending a response</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/resp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/resp/</guid>
      <description>The response must be sent using the Req object.
Cowboy provides two different ways of sending responses: either directly or by streaming the body. Response headers and body may be set in advance. The response is sent as soon as one of the reply or stream reply function is called.
Cowboy also provides a simplified interface for sending files. It can also send only specific parts of a file.
While only one response is allowed for every request, HTTP/2 introduced a mechanism that allows the server to push additional resources related to the response.</description>
    </item>
    
    <item>
      <title>Migrating from Ranch 1.x</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/migrating_from_1.x/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/migrating_from_1.x/</guid>
      <description>The changelog for Ranch releases before 1.6 can be found in this section.
1.5.0 Add transport functions getopts/2, getstat/1 and getstat/2  Fix ranch:info/0 and ranch:procs/2 in embedded mode  Prevent ranch_conns_sup from stopping on unexpected messages   1.4.0 Add new transport option num_acceptor  Deprecate ranch:start_listener/6 in favor of start_listener/5  Deprecate ranch:child_spec/6 in favor of child_spec/5   1.3.0 The version numbers 1.3.1 and 1.3.2 were later made to fix small mistakes made during the 1.</description>
    </item>
    
    <item>
      <title>Migrating from Ranch 1.x</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/migrating_from_1.x/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/migrating_from_1.x/</guid>
      <description>The changelog for Ranch releases before 1.6 can be found in this section.
1.5.0 Add transport functions getopts/2, getstat/1 and getstat/2  Fix ranch:info/0 and ranch:procs/2 in embedded mode  Prevent ranch_conns_sup from stopping on unexpected messages   1.4.0 Add new transport option num_acceptor  Deprecate ranch:start_listener/6 in favor of start_listener/5  Deprecate ranch:child_spec/6 in favor of child_spec/5   1.3.0 The version numbers 1.3.1 and 1.3.2 were later made to fix small mistakes made during the 1.</description>
    </item>
    
    <item>
      <title>Using cookies</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/cookies/</guid>
      <description>Cookies are a mechanism allowing applications to maintain state on top of the stateless HTTP protocol.
Cookies are a name/value store where the names and values are stored in plain text. They expire either after a delay or when the browser closes. They can be configured on a specific domain name or path, and restricted to secure resources (sent or downloaded over HTTPS), or restricted to the server (disallowing access from client-side scripts).</description>
    </item>
    
    <item>
      <title>Using cookies</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/cookies/</guid>
      <description>Cookies are a mechanism allowing applications to maintain state on top of the stateless HTTP protocol.
Cookies are a name/value store where the names and values are stored in plain text. They expire either after a delay or when the browser closes. They can be configured on a specific domain name or path, and restricted to secure resources (sent or downloaded over HTTPS), or restricted to the server (disallowing access from client-side scripts).</description>
    </item>
    
    <item>
      <title>Using cookies</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/cookies/</guid>
      <description>Cookies are a mechanism allowing applications to maintain state on top of the stateless HTTP protocol.
Cookies are a name/value store where the names and values are stored in plain text. They expire either after a delay or when the browser closes. They can be configured on a specific domain name or path, and restricted to secure resources (sent or downloaded over HTTPS), or restricted to the server (disallowing access from client-side scripts).</description>
    </item>
    
    <item>
      <title>Using cookies</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/cookies/</guid>
      <description>Cookies are a mechanism allowing applications to maintain state on top of the stateless HTTP protocol.
Cookies are a name/value store where the names and values are stored in plain text. They expire either after a delay or when the browser closes. They can be configured on a specific domain name or path, and restricted to secure resources (sent or downloaded over HTTPS), or restricted to the server (disallowing access from client-side scripts).</description>
    </item>
    
    <item>
      <title>Using cookies</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/cookies/</guid>
      <description>Cookies are a mechanism allowing applications to maintain state on top of the stateless HTTP protocol.
Cookies are a name/value store where the names and values are stored in plain text. They expire either after a delay or when the browser closes. They can be configured on a specific domain name or path, and restricted to secure resources (sent or downloaded over HTTPS), or restricted to the server (disallowing access from client-side scripts).</description>
    </item>
    
    <item>
      <title>Using cookies</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/cookies/</guid>
      <description>Cookies are a mechanism allowing applications to maintain state on top of the stateless HTTP protocol.
Cookies are a name/value store where the names and values are stored in plain text. They expire either after a delay or when the browser closes. They can be configured on a specific domain name or path, and restricted to secure resources (sent or downloaded over HTTPS), or restricted to the server (disallowing access from client-side scripts).</description>
    </item>
    
    <item>
      <title>Multipart requests</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/multipart/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/multipart/</guid>
      <description>Multipart originates from MIME, an Internet standard that extends the format of emails.
A multipart message is a list of parts. A part contains headers and a body. The body of the parts may be of any media type, and contain text or binary data. It is possible for parts to contain a multipart media type.
In the context of HTTP, multipart is most often used with the multipart/form-data media type.</description>
    </item>
    
    <item>
      <title>Multipart requests</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/multipart/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/multipart/</guid>
      <description>Multipart originates from MIME, an Internet standard that extends the format of emails.
A multipart message is a list of parts. A part contains headers and a body. The body of the parts may be of any media type, and contain text or binary data. It is possible for parts to contain a multipart media type.
In the context of HTTP, multipart is most often used with the multipart/form-data media type.</description>
    </item>
    
    <item>
      <title>Multipart requests</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/multipart/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/multipart/</guid>
      <description>Multipart originates from MIME, an Internet standard that extends the format of emails.
A multipart message is a list of parts. A part contains headers and a body. The body of the parts may be of any media type, and contain text or binary data. It is possible for parts to contain a multipart media type.
In the context of HTTP, multipart is most often used with the multipart/form-data media type.</description>
    </item>
    
    <item>
      <title>Multipart requests</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/multipart/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/multipart/</guid>
      <description>Multipart originates from MIME, an Internet standard that extends the format of emails.
A multipart message is a list of parts. A part contains headers and a body. The body of the parts may be of any media type, and contain text or binary data. It is possible for parts to contain a multipart media type.
In the context of HTTP, multipart is most often used with the multipart/form-data media type.</description>
    </item>
    
    <item>
      <title>Multipart requests</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/multipart/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/multipart/</guid>
      <description>Multipart originates from MIME, an Internet standard that extends the format of emails.
A multipart message is a list of parts. A part contains headers and a body. The body of the parts may be of any media type, and contain text or binary data. It is possible for parts to contain a multipart media type.
In the context of HTTP, multipart is most often used with the multipart/form-data media type.</description>
    </item>
    
    <item>
      <title>Multipart requests</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/multipart/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/multipart/</guid>
      <description>Multipart originates from MIME, an Internet standard that extends the format of emails.
A multipart message is a list of parts. A part contains headers and a body. The body of the parts may be of any media type, and contain text or binary data. It is possible for parts to contain a multipart media type.
In the context of HTTP, multipart is most often used with the multipart/form-data media type.</description>
    </item>
    
    <item>
      <title>REST principles</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/rest_principles/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/rest_principles/</guid>
      <description>This chapter will attempt to define the concepts behind REST and explain what makes a service RESTful.
REST is often confused with performing a distinct operation depending on the HTTP method, while using more than the GET and POST methods. That&amp;apos;s highly misguided at best.
We will first attempt to define REST and will look at what it means in the context of HTTP and the Web. For a more in-depth explanation of REST, you can read Roy T.</description>
    </item>
    
    <item>
      <title>REST principles</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/rest_principles/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/rest_principles/</guid>
      <description>This chapter will attempt to define the concepts behind REST and explain what makes a service RESTful.
REST is often confused with performing a distinct operation depending on the HTTP method, while using more than the GET and POST methods. That&amp;apos;s highly misguided at best.
We will first attempt to define REST and will look at what it means in the context of HTTP and the Web. For a more in-depth explanation of REST, you can read Roy T.</description>
    </item>
    
    <item>
      <title>REST principles</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/rest_principles/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/rest_principles/</guid>
      <description>This chapter will attempt to define the concepts behind REST and explain what makes a service RESTful.
REST is often confused with performing a distinct operation depending on the HTTP method, while using more than the GET and POST methods. That&amp;apos;s highly misguided at best.
We will first attempt to define REST and will look at what it means in the context of HTTP and the Web. For a more in-depth explanation of REST, you can read Roy T.</description>
    </item>
    
    <item>
      <title>REST principles</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/rest_principles/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/rest_principles/</guid>
      <description>This chapter will attempt to define the concepts behind REST and explain what makes a service RESTful.
REST is often confused with performing a distinct operation depending on the HTTP method, while using more than the GET and POST methods. That&amp;apos;s highly misguided at best.
We will first attempt to define REST and will look at what it means in the context of HTTP and the Web. For a more in-depth explanation of REST, you can read Roy T.</description>
    </item>
    
    <item>
      <title>REST principles</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/rest_principles/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/rest_principles/</guid>
      <description>This chapter will attempt to define the concepts behind REST and explain what makes a service RESTful.
REST is often confused with performing a distinct operation depending on the HTTP method, while using more than the GET and POST methods. That&amp;apos;s highly misguided at best.
We will first attempt to define REST and will look at what it means in the context of HTTP and the Web. For a more in-depth explanation of REST, you can read Roy T.</description>
    </item>
    
    <item>
      <title>REST principles</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/rest_principles/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/rest_principles/</guid>
      <description>This chapter will attempt to define the concepts behind REST and explain what makes a service RESTful.
REST is often confused with performing a distinct operation depending on the HTTP method, while using more than the GET and POST methods. That&amp;apos;s highly misguided at best.
We will first attempt to define REST and will look at what it means in the context of HTTP and the Web. For a more in-depth explanation of REST, you can read Roy T.</description>
    </item>
    
    <item>
      <title>REST handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/rest_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/rest_handlers/</guid>
      <description>REST is implemented in Cowboy as a sub protocol. The request is handled as a state machine with many optional callbacks describing the resource and modifying the machine&amp;apos;s behavior.
The REST handler is the recommended way to handle HTTP requests.
Initialization First, the init/2 callback is called. This callback is common to all handlers. To use REST for the current request, this function must return a cowboy_rest tuple.
init(Req, State) -&amp;gt; {cowboy_rest, Req, State}.</description>
    </item>
    
    <item>
      <title>REST handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/rest_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/rest_handlers/</guid>
      <description>REST is implemented in Cowboy as a sub protocol. The request is handled as a state machine with many optional callbacks describing the resource and modifying the machine&amp;apos;s behavior.
The REST handler is the recommended way to handle HTTP requests.
Initialization First, the init/2 callback is called. This callback is common to all handlers. To use REST for the current request, this function must return a cowboy_rest tuple.
init(Req, State) -&amp;gt; {cowboy_rest, Req, State}.</description>
    </item>
    
    <item>
      <title>REST handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/rest_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/rest_handlers/</guid>
      <description>REST is implemented in Cowboy as a sub protocol. The request is handled as a state machine with many optional callbacks describing the resource and modifying the machine&amp;apos;s behavior.
The REST handler is the recommended way to handle HTTP requests.
Initialization First, the init/2 callback is called. This callback is common to all handlers. To use REST for the current request, this function must return a cowboy_rest tuple.
init(Req, State) -&amp;gt; {cowboy_rest, Req, State}.</description>
    </item>
    
    <item>
      <title>REST handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/rest_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/rest_handlers/</guid>
      <description>REST is implemented in Cowboy as a sub protocol. The request is handled as a state machine with many optional callbacks describing the resource and modifying the machine&amp;apos;s behavior.
The REST handler is the recommended way to handle HTTP requests.
Initialization First, the init/2 callback is called. This callback is common to all handlers. To use REST for the current request, this function must return a cowboy_rest tuple.
init(Req, State) -&amp;gt; {cowboy_rest, Req, State}.</description>
    </item>
    
    <item>
      <title>REST handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/rest_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/rest_handlers/</guid>
      <description>REST is implemented in Cowboy as a sub protocol. The request is handled as a state machine with many optional callbacks describing the resource and modifying the machine&amp;apos;s behavior.
The REST handler is the recommended way to handle HTTP requests.
Initialization First, the init/2 callback is called. This callback is common to all handlers. To use REST for the current request, this function must return a cowboy_rest tuple.
init(Req, State) -&amp;gt; {cowboy_rest, Req, State}.</description>
    </item>
    
    <item>
      <title>REST handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/rest_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/rest_handlers/</guid>
      <description>REST is implemented in Cowboy as a sub protocol. The request is handled as a state machine with many optional callbacks describing the resource and modifying the machine&amp;apos;s behavior.
The REST handler is the recommended way to handle HTTP requests.
Initialization First, the init/2 callback is called. This callback is common to all handlers. To use REST for the current request, this function must return a cowboy_rest tuple.
init(Req, State) -&amp;gt; {cowboy_rest, Req, State}.</description>
    </item>
    
    <item>
      <title>REST flowcharts</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/rest_flowcharts/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/rest_flowcharts/</guid>
      <description>This chapter will explain the REST handler state machine through a number of different diagrams.
There are four main paths that requests may follow. One for the method OPTIONS; one for the methods GET and HEAD; one for the methods PUT, POST and PATCH; and one for the method DELETE.
All paths start with the &amp;quot;Start&amp;quot; diagram, and all paths excluding the OPTIONS path go through the &amp;quot;Content negotiation&amp;quot; diagram and optionally the &amp;quot;Conditional requests&amp;quot; diagram if the resource exists.</description>
    </item>
    
    <item>
      <title>REST flowcharts</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/rest_flowcharts/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/rest_flowcharts/</guid>
      <description>This chapter will explain the REST handler state machine through a number of different diagrams.
There are four main paths that requests may follow. One for the method OPTIONS; one for the methods GET and HEAD; one for the methods PUT, POST and PATCH; and one for the method DELETE.
All paths start with the &amp;quot;Start&amp;quot; diagram, and all paths excluding the OPTIONS path go through the &amp;quot;Content negotiation&amp;quot; diagram and optionally the &amp;quot;Conditional requests&amp;quot; diagram if the resource exists.</description>
    </item>
    
    <item>
      <title>REST flowcharts</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/rest_flowcharts/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/rest_flowcharts/</guid>
      <description>This chapter will explain the REST handler state machine through a number of different diagrams.
There are four main paths that requests may follow. One for the method OPTIONS; one for the methods GET and HEAD; one for the methods PUT, POST and PATCH; and one for the method DELETE.
All paths start with the &amp;quot;Start&amp;quot; diagram, and all paths excluding the OPTIONS path go through the &amp;quot;Content negotiation&amp;quot; diagram and optionally the &amp;quot;Conditional requests&amp;quot; diagram if the resource exists.</description>
    </item>
    
    <item>
      <title>REST flowcharts</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/rest_flowcharts/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/rest_flowcharts/</guid>
      <description>This chapter will explain the REST handler state machine through a number of different diagrams.
There are four main paths that requests may follow. One for the method OPTIONS; one for the methods GET and HEAD; one for the methods PUT, POST and PATCH; and one for the method DELETE.
All paths start with the &amp;quot;Start&amp;quot; diagram, and all paths excluding the OPTIONS path go through the &amp;quot;Content negotiation&amp;quot; diagram and optionally the &amp;quot;Conditional requests&amp;quot; diagram if the resource exists.</description>
    </item>
    
    <item>
      <title>REST flowcharts</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/rest_flowcharts/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/rest_flowcharts/</guid>
      <description>This chapter will explain the REST handler state machine through a number of different diagrams.
There are four main paths that requests may follow. One for the method OPTIONS; one for the methods GET and HEAD; one for the methods PUT, POST and PATCH; and one for the method DELETE.
All paths start with the &amp;quot;Start&amp;quot; diagram, and all paths excluding the OPTIONS path go through the &amp;quot;Content negotiation&amp;quot; diagram and optionally the &amp;quot;Conditional requests&amp;quot; diagram if the resource exists.</description>
    </item>
    
    <item>
      <title>REST flowcharts</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/rest_flowcharts/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/rest_flowcharts/</guid>
      <description>This chapter will explain the REST handler state machine through a number of different diagrams.
There are four main paths that requests may follow. One for the method OPTIONS; one for the methods GET and HEAD; one for the methods PUT, POST and PATCH; and one for the method DELETE.
All paths start with the &amp;quot;Start&amp;quot; diagram, and all paths excluding the OPTIONS path go through the &amp;quot;Content negotiation&amp;quot; diagram and optionally the &amp;quot;Conditional requests&amp;quot; diagram if the resource exists.</description>
    </item>
    
    <item>
      <title>Designing a resource handler</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/resource_design/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/resource_design/</guid>
      <description>This chapter aims to provide you with a list of questions you must answer in order to write a good resource handler. It is meant to be usable as a step by step guide.
The service Can the service become unavailable, and when it does, can we detect it? For example, database connectivity problems may be detected early. We may also have planned outages of all or parts of the system.</description>
    </item>
    
    <item>
      <title>Designing a resource handler</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/resource_design/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/resource_design/</guid>
      <description>This chapter aims to provide you with a list of questions you must answer in order to write a good resource handler. It is meant to be usable as a step by step guide.
The service Can the service become unavailable, and when it does, can we detect it? For example, database connectivity problems may be detected early. We may also have planned outages of all or parts of the system.</description>
    </item>
    
    <item>
      <title>Designing a resource handler</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/resource_design/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/resource_design/</guid>
      <description>This chapter aims to provide you with a list of questions you must answer in order to write a good resource handler. It is meant to be usable as a step by step guide.
The service Can the service become unavailable, and when it does, can we detect it? For example, database connectivity problems may be detected early. We may also have planned outages of all or parts of the system.</description>
    </item>
    
    <item>
      <title>Designing a resource handler</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/resource_design/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/resource_design/</guid>
      <description>This chapter aims to provide you with a list of questions you must answer in order to write a good resource handler. It is meant to be usable as a step by step guide.
The service Can the service become unavailable, and when it does, can we detect it? For example, database connectivity problems may be detected early. We may also have planned outages of all or parts of the system.</description>
    </item>
    
    <item>
      <title>Designing a resource handler</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/resource_design/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/resource_design/</guid>
      <description>This chapter aims to provide you with a list of questions you must answer in order to write a good resource handler. It is meant to be usable as a step by step guide.
The service Can the service become unavailable, and when it does, can we detect it? For example, database connectivity problems may be detected early. We may also have planned outages of all or parts of the system.</description>
    </item>
    
    <item>
      <title>Designing a resource handler</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/resource_design/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/resource_design/</guid>
      <description>This chapter aims to provide you with a list of questions you must answer in order to write a good resource handler. It is meant to be usable as a step by step guide.
The service Can the service become unavailable, and when it does, can we detect it? For example, database connectivity problems may be detected early. We may also have planned outages of all or parts of the system.</description>
    </item>
    
    <item>
      <title>The Websocket protocol</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/ws_protocol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/ws_protocol/</guid>
      <description>This chapter explains what Websocket is and why it is a vital component of soft realtime Web applications.
Description Websocket is an extension to HTTP that emulates plain TCP connections between the client, typically a Web browser, and the server. It uses the HTTP Upgrade mechanism to establish the connection.
Websocket connections are fully asynchronous, unlike HTTP/1.1 (synchronous) and HTTP/2 (asynchronous, but the server can only initiate streams in response to requests).</description>
    </item>
    
    <item>
      <title>The Websocket protocol</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/ws_protocol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/ws_protocol/</guid>
      <description>This chapter explains what Websocket is and why it is a vital component of soft realtime Web applications.
Description Websocket is an extension to HTTP that emulates plain TCP connections between the client, typically a Web browser, and the server. It uses the HTTP Upgrade mechanism to establish the connection.
Websocket connections are fully asynchronous, unlike HTTP/1.1 (synchronous) and HTTP/2 (asynchronous, but the server can only initiate streams in response to requests).</description>
    </item>
    
    <item>
      <title>The Websocket protocol</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/ws_protocol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/ws_protocol/</guid>
      <description>This chapter explains what Websocket is and why it is a vital component of soft realtime Web applications.
Description Websocket is an extension to HTTP that emulates plain TCP connections between the client, typically a Web browser, and the server. It uses the HTTP Upgrade mechanism to establish the connection.
Websocket connections are fully asynchronous, unlike HTTP/1.1 (synchronous) and HTTP/2 (asynchronous, but the server can only initiate streams in response to requests).</description>
    </item>
    
    <item>
      <title>The Websocket protocol</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/ws_protocol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/ws_protocol/</guid>
      <description>This chapter explains what Websocket is and why it is a vital component of soft realtime Web applications.
Description Websocket is an extension to HTTP that emulates plain TCP connections between the client, typically a Web browser, and the server. It uses the HTTP Upgrade mechanism to establish the connection.
Websocket connections are fully asynchronous, unlike HTTP/1.1 (synchronous) and HTTP/2 (asynchronous, but the server can only initiate streams in response to requests).</description>
    </item>
    
    <item>
      <title>The Websocket protocol</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/ws_protocol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/ws_protocol/</guid>
      <description>This chapter explains what Websocket is and why it is a vital component of soft realtime Web applications.
Description Websocket is an extension to HTTP that emulates plain TCP connections between the client, typically a Web browser, and the server. It uses the HTTP Upgrade mechanism to establish the connection.
Websocket connections are fully asynchronous, unlike HTTP/1.1 (synchronous) and HTTP/2 (asynchronous, but the server can only initiate streams in response to requests).</description>
    </item>
    
    <item>
      <title>The Websocket protocol</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/ws_protocol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/ws_protocol/</guid>
      <description>This chapter explains what Websocket is and why it is a vital component of soft realtime Web applications.
Description Websocket is an extension to HTTP that emulates plain TCP connections between the client, typically a Web browser, and the server. It uses the HTTP Upgrade mechanism to establish the connection.
Websocket connections are fully asynchronous, unlike HTTP/1.1 (synchronous) and HTTP/2 (asynchronous, but the server can only initiate streams in response to requests).</description>
    </item>
    
    <item>
      <title>Websocket handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/ws_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/ws_handlers/</guid>
      <description>Websocket handlers provide an interface for upgrading HTTP/1.1 connections to Websocket and sending or receiving frames on the Websocket connection.
As Websocket connections are established through the HTTP/1.1 upgrade mechanism, Websocket handlers need to be able to first receive the HTTP request for the upgrade, before switching to Websocket and taking over the connection. They can then receive or send Websocket frames, handle incoming Erlang messages or close the connection.</description>
    </item>
    
    <item>
      <title>Websocket handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/ws_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/ws_handlers/</guid>
      <description>Websocket handlers provide an interface for upgrading HTTP/1.1 connections to Websocket and sending or receiving frames on the Websocket connection.
As Websocket connections are established through the HTTP/1.1 upgrade mechanism, Websocket handlers need to be able to first receive the HTTP request for the upgrade, before switching to Websocket and taking over the connection. They can then receive or send Websocket frames, handle incoming Erlang messages or close the connection.</description>
    </item>
    
    <item>
      <title>Websocket handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/ws_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/ws_handlers/</guid>
      <description>Websocket handlers provide an interface for upgrading HTTP/1.1 connections to Websocket and sending or receiving frames on the Websocket connection.
As Websocket connections are established through the HTTP/1.1 upgrade mechanism, Websocket handlers need to be able to first receive the HTTP request for the upgrade, before switching to Websocket and taking over the connection. They can then receive or send Websocket frames, handle incoming Erlang messages or close the connection.</description>
    </item>
    
    <item>
      <title>Websocket handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/ws_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/ws_handlers/</guid>
      <description>Websocket handlers provide an interface for upgrading HTTP/1.1 connections to Websocket and sending or receiving frames on the Websocket connection.
As Websocket connections are established through the HTTP/1.1 upgrade mechanism, Websocket handlers need to be able to first receive the HTTP request for the upgrade, before switching to Websocket and taking over the connection. They can then receive or send Websocket frames, handle incoming Erlang messages or close the connection.</description>
    </item>
    
    <item>
      <title>Websocket handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/ws_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/ws_handlers/</guid>
      <description>Websocket handlers provide an interface for upgrading HTTP/1.1 connections to Websocket and sending or receiving frames on the Websocket connection.
As Websocket connections are established through the HTTP/1.1 upgrade mechanism, Websocket handlers need to be able to first receive the HTTP request for the upgrade, before switching to Websocket and taking over the connection. They can then receive or send Websocket frames, handle incoming Erlang messages or close the connection.</description>
    </item>
    
    <item>
      <title>Websocket handlers</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/ws_handlers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/ws_handlers/</guid>
      <description>Websocket handlers provide an interface for upgrading HTTP/1.1 connections to Websocket and sending or receiving frames on the Websocket connection.
As Websocket connections are established through the HTTP/1.1 upgrade mechanism, Websocket handlers need to be able to first receive the HTTP request for the upgrade, before switching to Websocket and taking over the connection. They can then receive or send Websocket frames, handle incoming Erlang messages or close the connection.</description>
    </item>
    
    <item>
      <title>Streams</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/streams/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/streams/</guid>
      <description>A stream is the set of messages that form an HTTP request/response pair.
The term stream comes from HTTP/2. In Cowboy, it is also used when talking about HTTP/1.1 or HTTP/1.0. It should not be confused with streaming the request or response body.
All versions of HTTP allow clients to initiate streams. HTTP/2 is the only one also allowing servers, through its server push feature. Both client and server-initiated streams go through the same process in Cowboy.</description>
    </item>
    
    <item>
      <title>Streams</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/streams/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/streams/</guid>
      <description>A stream is the set of messages that form an HTTP request/response pair.
The term stream comes from HTTP/2. In Cowboy, it is also used when talking about HTTP/1.1 or HTTP/1.0. It should not be confused with streaming the request or response body.
All versions of HTTP allow clients to initiate streams. HTTP/2 is the only one also allowing servers, through its server push feature. Both client and server-initiated streams go through the same process in Cowboy.</description>
    </item>
    
    <item>
      <title>Streams</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/streams/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/streams/</guid>
      <description>A stream is the set of messages that form an HTTP request/response pair.
The term stream comes from HTTP/2. In Cowboy, it is also used when talking about HTTP/1.1 or HTTP/1.0. It should not be confused with streaming the request or response body.
All versions of HTTP allow clients to initiate streams. HTTP/2 is the only one also allowing servers, through its server push feature. Both client and server-initiated streams go through the same process in Cowboy.</description>
    </item>
    
    <item>
      <title>Streams</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/streams/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/streams/</guid>
      <description>A stream is the set of messages that form an HTTP request/response pair.
The term stream comes from HTTP/2. In Cowboy, it is also used when talking about HTTP/1.1 or HTTP/1.0. It should not be confused with streaming the request or response body.
All versions of HTTP allow clients to initiate streams. HTTP/2 is the only one also allowing servers, through its server push feature. Both client and server-initiated streams go through the same process in Cowboy.</description>
    </item>
    
    <item>
      <title>Streams</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/streams/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/streams/</guid>
      <description>A stream is the set of messages that form an HTTP request/response pair.
The term stream comes from HTTP/2. In Cowboy, it is also used when talking about HTTP/1.1 or HTTP/1.0. It should not be confused with streaming the request or response body.
All versions of HTTP allow clients to initiate streams. HTTP/2 is the only one also allowing servers, through its server push feature. Both client and server-initiated streams go through the same process in Cowboy.</description>
    </item>
    
    <item>
      <title>Streams</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/streams/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/streams/</guid>
      <description>A stream is the set of messages that form an HTTP request/response pair.
The term stream comes from HTTP/2. In Cowboy, it is also used when talking about HTTP/1.1 or HTTP/1.0. It should not be confused with streaming the request or response body.
All versions of HTTP allow clients to initiate streams. HTTP/2 is the only one also allowing servers, through its server push feature. Both client and server-initiated streams go through the same process in Cowboy.</description>
    </item>
    
    <item>
      <title>Middlewares</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/middlewares/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/middlewares/</guid>
      <description>Cowboy delegates the request processing to middleware components. By default, two middlewares are defined, for the routing and handling of the request, as is detailed in most of this guide.
Middlewares give you complete control over how requests are to be processed. You can add your own middlewares to the mix or completely change the chain of middlewares as needed.
Cowboy will execute all middlewares in the given order, unless one of them decides to stop processing.</description>
    </item>
    
    <item>
      <title>Middlewares</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/middlewares/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/middlewares/</guid>
      <description>Cowboy delegates the request processing to middleware components. By default, two middlewares are defined, for the routing and handling of the request, as is detailed in most of this guide.
Middlewares give you complete control over how requests are to be processed. You can add your own middlewares to the mix or completely change the chain of middlewares as needed.
Cowboy will execute all middlewares in the given order, unless one of them decides to stop processing.</description>
    </item>
    
    <item>
      <title>Middlewares</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/middlewares/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/middlewares/</guid>
      <description>Cowboy delegates the request processing to middleware components. By default, two middlewares are defined, for the routing and handling of the request, as is detailed in most of this guide.
Middlewares give you complete control over how requests are to be processed. You can add your own middlewares to the mix or completely change the chain of middlewares as needed.
Cowboy will execute all middlewares in the given order, unless one of them decides to stop processing.</description>
    </item>
    
    <item>
      <title>Middlewares</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/middlewares/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/middlewares/</guid>
      <description>Cowboy delegates the request processing to middleware components. By default, two middlewares are defined, for the routing and handling of the request, as is detailed in most of this guide.
Middlewares give you complete control over how requests are to be processed. You can add your own middlewares to the mix or completely change the chain of middlewares as needed.
Cowboy will execute all middlewares in the given order, unless one of them decides to stop processing.</description>
    </item>
    
    <item>
      <title>Middlewares</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/middlewares/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/middlewares/</guid>
      <description>Cowboy delegates the request processing to middleware components. By default, two middlewares are defined, for the routing and handling of the request, as is detailed in most of this guide.
Middlewares give you complete control over how requests are to be processed. You can add your own middlewares to the mix or completely change the chain of middlewares as needed.
Cowboy will execute all middlewares in the given order, unless one of them decides to stop processing.</description>
    </item>
    
    <item>
      <title>Middlewares</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/middlewares/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/middlewares/</guid>
      <description>Cowboy delegates the request processing to middleware components. By default, two middlewares are defined, for the routing and handling of the request, as is detailed in most of this guide.
Middlewares give you complete control over how requests are to be processed. You can add your own middlewares to the mix or completely change the chain of middlewares as needed.
Cowboy will execute all middlewares in the given order, unless one of them decides to stop processing.</description>
    </item>
    
    <item>
      <title>Changes since Cowboy 2.2</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/migrating_from_2.2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/migrating_from_2.2/</guid>
      <description>The following patch versions were released since Cowboy 2.2:
Cowboy 2.2.2 While fixing the miscount in the previous patch release an issue was introduced where HTTP/2 bodies could be sent out of orders when using iolists. This has been corrected.   Cowboy 2.2.1 Colons are now allowed within path segments in routes provided to cowboy_router:compile/1 as long as they are not the first character of the path segment.  The cowboy_req:delete_resp_header/2 function will no longer crash when no response header was set before calling it.</description>
    </item>
    
    <item>
      <title>Changes since Cowboy 2.6</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.6/</guid>
      <description>The following patch versions were released since Cowboy 2.6:
Cowboy 2.6.3 This release updates Cowlib to 2.7.3 to fix the vsn value in the cowlib.app file that was causing issues to Elixir users.
Cowboy 2.6.2 This release updates Cowlib to 2.7.2.
A bug in the HTTP/2 code that resulted in the failure to fully send iolist response bodies has been fixed. Cowboy would just wait indefinitely in those cases.
Cowboy will now use the host header when the HTTP/2 :authority pseudo header is missing.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.2 to 2.3</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/migrating_from_2.2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/migrating_from_2.2/</guid>
      <description>Cowboy 2.3 focused on making the Cowboy processes behave properly according to OTP principles. This version is a very good milestone toward that goal and most of everything should now work. Release upgrades and a few details will be improved in future versions.
Features added Add support for all functions from the module sys. Note that Cowboy currently does not implement the sys debugging mechanisms as tracing is recommended instead.  Add a max_frame_size option for Websocket handlers to close the connection when the client attempts to send a frame that&amp;apos;s too large.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.3 to 2.4</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.3/</guid>
      <description>Cowboy 2.4 focused on improving the HTTP/2 implementation. All existing tests from RFC7540 and the h2spec test suite now all pass. Numerous options have been added to control SETTINGS and related behavior. In addition experimental support for Websocket over HTTP/2 was added.
Features added Add experimental support for Websocket over HTTP/2. You can use the enable_connect_protocol option to enable. It implements the following draft: https://tools.ietf.org/html/draft-ietf-httpbis-h2-websockets-01  Add options max_decode_table_size and max_encode_table_size to restrict the size of the HPACK compression dictionary.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.4 to 2.5</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/migrating_from_2.4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/migrating_from_2.4/</guid>
      <description>Cowboy 2.5 focused on making the test suites pass. A variety of new features, fixes and improvements have also been worked on.
Features added Add option linger_timeout to control how long Cowboy will wait before closing the socket when shutting down the connection. This helps avoid the TCP reset problem HTTP/1.1 suffers from. The default is now 1000 ms.  It is now possible to stream a response body without using chunked transfer-encoding when the protocol is HTTP/1.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.6 to 2.7</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.6/</guid>
      <description>Cowboy 2.7 improves the HTTP/2 code with optimizations around the sending of DATA and WINDOW_UPDATE frames; graceful shutdown of the connection when the client is going away; and rate limiting mechanisms. New options and mechanisms have also been added to control the amount of memory Cowboy ends up using with both HTTP/1.1 and HTTP/2. Much, but not all, of this work was done to address HTTP/2 CVEs about potential denial of service.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.1 to 2.2</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/migrating_from_2.1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/migrating_from_2.1/</guid>
      <description>Cowboy 2.2 focused on adding features required for writing gRPC servers and on completing test suites for the core HTTP RFCs, fixing many bugs along the way.
Features added Add support for sending trailers at the end of response bodies. Trailers are additional header fields that may be sent after the body to add more information to the response. Their usage is required in gRPC servers. They are optional and may be discarded in other scenarios (for example if the request goes through an HTTP/1.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.1 to 2.2</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/migrating_from_2.1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/migrating_from_2.1/</guid>
      <description>Cowboy 2.2 focused on adding features required for writing gRPC servers and on completing test suites for the core HTTP RFCs, fixing many bugs along the way.
Features added Add support for sending trailers at the end of response bodies. Trailers are additional header fields that may be sent after the body to add more information to the response. Their usage is required in gRPC servers. They are optional and may be discarded in other scenarios (for example if the request goes through an HTTP/1.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.2 to 2.3</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.2/</guid>
      <description>Cowboy 2.3 focused on making the Cowboy processes behave properly according to OTP principles. This version is a very good milestone toward that goal and most of everything should now work. Release upgrades and a few details will be improved in future versions.
Features added Add support for all functions from the module sys. Note that Cowboy currently does not implement the sys debugging mechanisms as tracing is recommended instead.  Add a max_frame_size option for Websocket handlers to close the connection when the client attempts to send a frame that&amp;apos;s too large.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.3 to 2.4</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/migrating_from_2.3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/migrating_from_2.3/</guid>
      <description>Cowboy 2.4 focused on improving the HTTP/2 implementation. All existing tests from RFC7540 and the h2spec test suite now all pass. Numerous options have been added to control SETTINGS and related behavior. In addition experimental support for Websocket over HTTP/2 was added.
Features added Add experimental support for Websocket over HTTP/2. You can use the enable_connect_protocol option to enable. It implements the following draft: https://tools.ietf.org/html/draft-ietf-httpbis-h2-websockets-01  Add options max_decode_table_size and max_encode_table_size to restrict the size of the HPACK compression dictionary.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.5 to 2.6</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.5/</guid>
      <description>Cowboy 2.6 greatly refactored the HTTP/2 code, a large part of which was moved to Cowlib and is now used by both the Cowboy server and the Gun client.
A large number of tickets were also closed which resulted in many bugs fixed and many features and options added, although some of them are still experimental.
Features added Add support for the PROXY protocol header. It can be enabled via the proxy_header option.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.5 to 2.6</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.5/</guid>
      <description>Cowboy 2.6 greatly refactored the HTTP/2 code, a large part of which was moved to Cowlib and is now used by both the Cowboy server and the Gun client.
A large number of tickets were also closed which resulted in many bugs fixed and many features and options added, although some of them are still experimental.
Features added Add support for the PROXY protocol header. It can be enabled via the proxy_header option.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.0 to 2.1</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/migrating_from_2.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/migrating_from_2.0/</guid>
      <description>Cowboy 2.1 focused on adding features that were temporarily removed in Cowboy 2.0. A number of bugs found in the 2.0 release were also fixed.
Features added It is now possible to obtain the client TLS certificate and the local IP/port for the connection from the Req object.  Informational responses (1XX responses) can now be sent. They must be sent before initiating the final response.  The expect: 100-continue header is now handled automatically.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.0 to 2.1</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/migrating_from_2.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/migrating_from_2.0/</guid>
      <description>Cowboy 2.1 focused on adding features that were temporarily removed in Cowboy 2.0. A number of bugs found in the 2.0 release were also fixed.
Features added It is now possible to obtain the client TLS certificate and the local IP/port for the connection from the Req object.  Informational responses (1XX responses) can now be sent. They must be sent before initiating the final response.  The expect: 100-continue header is now handled automatically.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.1 to 2.2</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.1/</guid>
      <description>Cowboy 2.2 focused on adding features required for writing gRPC servers and on completing test suites for the core HTTP RFCs, fixing many bugs along the way.
Features added Add support for sending trailers at the end of response bodies. Trailers are additional header fields that may be sent after the body to add more information to the response. Their usage is required in gRPC servers. They are optional and may be discarded in other scenarios (for example if the request goes through an HTTP/1.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.2 to 2.3</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/migrating_from_2.2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/migrating_from_2.2/</guid>
      <description>Cowboy 2.3 focused on making the Cowboy processes behave properly according to OTP principles. This version is a very good milestone toward that goal and most of everything should now work. Release upgrades and a few details will be improved in future versions.
Features added Add support for all functions from the module sys. Note that Cowboy currently does not implement the sys debugging mechanisms as tracing is recommended instead.  Add a max_frame_size option for Websocket handlers to close the connection when the client attempts to send a frame that&amp;apos;s too large.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.4 to 2.5</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.4/</guid>
      <description>Cowboy 2.5 focused on making the test suites pass. A variety of new features, fixes and improvements have also been worked on.
Features added Add option linger_timeout to control how long Cowboy will wait before closing the socket when shutting down the connection. This helps avoid the TCP reset problem HTTP/1.1 suffers from. The default is now 1000 ms.  It is now possible to stream a response body without using chunked transfer-encoding when the protocol is HTTP/1.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.4 to 2.5</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.4/</guid>
      <description>Cowboy 2.5 focused on making the test suites pass. A variety of new features, fixes and improvements have also been worked on.
Features added Add option linger_timeout to control how long Cowboy will wait before closing the socket when shutting down the connection. This helps avoid the TCP reset problem HTTP/1.1 suffers from. The default is now 1000 ms.  It is now possible to stream a response body without using chunked transfer-encoding when the protocol is HTTP/1.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 1.0 to 2.0</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/migrating_from_1.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/migrating_from_1.0/</guid>
      <description>A lot has changed between Cowboy 1.0 and 2.0. The cowboy_req interface in particular has seen a massive revamp. Hooks are gone, their functionality can now be achieved via stream handlers.
The documentation has seen great work, in particular the manual. Each module and each function now has its own dedicated manual page with full details and examples.
Compatibility Compatibility with Erlang/OTP R16, 17 and 18 has been dropped. Erlang/OTP 19.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 1.0 to 2.0</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/migrating_from_1.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/migrating_from_1.0/</guid>
      <description>A lot has changed between Cowboy 1.0 and 2.0. The cowboy_req interface in particular has seen a massive revamp. Hooks are gone, their functionality can now be achieved via stream handlers.
The documentation has seen great work, in particular the manual. Each module and each function now has its own dedicated manual page with full details and examples.
Compatibility Compatibility with Erlang/OTP R16, 17 and 18 has been dropped. Erlang/OTP 19.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.0 to 2.1</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_2.0/</guid>
      <description>Cowboy 2.1 focused on adding features that were temporarily removed in Cowboy 2.0. A number of bugs found in the 2.0 release were also fixed.
Features added It is now possible to obtain the client TLS certificate and the local IP/port for the connection from the Req object.  Informational responses (1XX responses) can now be sent. They must be sent before initiating the final response.  The expect: 100-continue header is now handled automatically.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.1 to 2.2</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/migrating_from_2.1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/migrating_from_2.1/</guid>
      <description>Cowboy 2.2 focused on adding features required for writing gRPC servers and on completing test suites for the core HTTP RFCs, fixing many bugs along the way.
Features added Add support for sending trailers at the end of response bodies. Trailers are additional header fields that may be sent after the body to add more information to the response. Their usage is required in gRPC servers. They are optional and may be discarded in other scenarios (for example if the request goes through an HTTP/1.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.3 to 2.4</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.3/</guid>
      <description>Cowboy 2.4 focused on improving the HTTP/2 implementation. All existing tests from RFC7540 and the h2spec test suite now all pass. Numerous options have been added to control SETTINGS and related behavior. In addition experimental support for Websocket over HTTP/2 was added.
Features added Add experimental support for Websocket over HTTP/2. You can use the enable_connect_protocol option to enable. It implements the following draft: https://tools.ietf.org/html/draft-ietf-httpbis-h2-websockets-01  Add options max_decode_table_size and max_encode_table_size to restrict the size of the HPACK compression dictionary.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.3 to 2.4</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.3/</guid>
      <description>Cowboy 2.4 focused on improving the HTTP/2 implementation. All existing tests from RFC7540 and the h2spec test suite now all pass. Numerous options have been added to control SETTINGS and related behavior. In addition experimental support for Websocket over HTTP/2 was added.
Features added Add experimental support for Websocket over HTTP/2. You can use the enable_connect_protocol option to enable. It implements the following draft: https://tools.ietf.org/html/draft-ietf-httpbis-h2-websockets-01  Add options max_decode_table_size and max_encode_table_size to restrict the size of the HPACK compression dictionary.</description>
    </item>
    
    <item>
      <title>HTTP and other specifications</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/specs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/specs/</guid>
      <description>This chapter intends to list all the specification documents for or related to HTTP.
HTTP IANA Registries HTTP Method Registry  HTTP Status Code Registry  Message Headers  HTTP Parameters  HTTP Alt-Svc Parameter Registry  HTTP Authentication Scheme Registry  HTTP Cache Directive Registry  HTTP Digest Algorithm Values  HTTP Origin-Bound Authentication Device Identifier Types  HTTP Upgrade Token Registry  HTTP Warn Codes  HTTP/2 Parameters  WebSocket Protocol Registries   Current CORS: Cross-Origin Resource Sharing  CSP2: Content Security Policy Level 2  DNT: Tracking Preference Expression (DNT)  eventsource: Server-Sent Events  Form content types: Form content types  Preload: Preload  REST: Fielding&amp;apos;s Dissertation  RFC 1945: HTTP/1.</description>
    </item>
    
    <item>
      <title>HTTP and other specifications</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/specs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/specs/</guid>
      <description>This chapter intends to list all the specification documents for or related to HTTP.
HTTP IANA Registries HTTP Method Registry  HTTP Status Code Registry  Message Headers  HTTP Parameters  HTTP Alt-Svc Parameter Registry  HTTP Authentication Scheme Registry  HTTP Cache Directive Registry  HTTP Digest Algorithm Values  HTTP Origin-Bound Authentication Device Identifier Types  HTTP Upgrade Token Registry  HTTP Warn Codes  HTTP/2 Parameters  WebSocket Protocol Registries   Current CORS: Cross-Origin Resource Sharing  CSP2: Content Security Policy Level 2  DNT: Tracking Preference Expression (DNT)  eventsource: Server-Sent Events  Form content types: Form content types  Preload: Preload  PROXY: The PROXY protocol  REST: Fielding&amp;apos;s Dissertation  RFC 1945: HTTP/1.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 1.0 to 2.0</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_1.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/migrating_from_1.0/</guid>
      <description>A lot has changed between Cowboy 1.0 and 2.0. The cowboy_req interface in particular has seen a massive revamp. Hooks are gone, their functionality can now be achieved via stream handlers.
The documentation has seen great work, in particular the manual. Each module and each function now has its own dedicated manual page with full details and examples.
Compatibility Compatibility with Erlang/OTP R16, 17 and 18 has been dropped. Erlang/OTP 19.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.0 to 2.1</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/migrating_from_2.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/migrating_from_2.0/</guid>
      <description>Cowboy 2.1 focused on adding features that were temporarily removed in Cowboy 2.0. A number of bugs found in the 2.0 release were also fixed.
Features added It is now possible to obtain the client TLS certificate and the local IP/port for the connection from the Req object.  Informational responses (1XX responses) can now be sent. They must be sent before initiating the final response.  The expect: 100-continue header is now handled automatically.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.2 to 2.3</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.2/</guid>
      <description>Cowboy 2.3 focused on making the Cowboy processes behave properly according to OTP principles. This version is a very good milestone toward that goal and most of everything should now work. Release upgrades and a few details will be improved in future versions.
Features added Add support for all functions from the module sys. Note that Cowboy currently does not implement the sys debugging mechanisms as tracing is recommended instead.  Add a max_frame_size option for Websocket handlers to close the connection when the client attempts to send a frame that&amp;apos;s too large.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.2 to 2.3</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.2/</guid>
      <description>Cowboy 2.3 focused on making the Cowboy processes behave properly according to OTP principles. This version is a very good milestone toward that goal and most of everything should now work. Release upgrades and a few details will be improved in future versions.
Features added Add support for all functions from the module sys. Note that Cowboy currently does not implement the sys debugging mechanisms as tracing is recommended instead.  Add a max_frame_size option for Websocket handlers to close the connection when the client attempts to send a frame that&amp;apos;s too large.</description>
    </item>
    
    <item>
      <title>HTTP and other specifications</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/specs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/specs/</guid>
      <description>This chapter intends to list all the specification documents for or related to HTTP.
HTTP IANA Registries HTTP Method Registry  HTTP Status Code Registry  Message Headers  HTTP Parameters  HTTP Alt-Svc Parameter Registry  HTTP Authentication Scheme Registry  HTTP Cache Directive Registry  HTTP Digest Algorithm Values  HTTP Origin-Bound Authentication Device Identifier Types  HTTP Upgrade Token Registry  HTTP Warn Codes  HTTP/2 Parameters  WebSocket Protocol Registries   Current CORS: Cross-Origin Resource Sharing  CSP2: Content Security Policy Level 2  DNT: Tracking Preference Expression (DNT)  eventsource: Server-Sent Events  Form content types: Form content types  Preload: Preload  PROXY: The PROXY protocol  REST: Fielding&amp;apos;s Dissertation  RFC 1945: HTTP/1.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 1.0 to 2.0</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/migrating_from_1.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/migrating_from_1.0/</guid>
      <description>A lot has changed between Cowboy 1.0 and 2.0. The cowboy_req interface in particular has seen a massive revamp. Hooks are gone, their functionality can now be achieved via stream handlers.
The documentation has seen great work, in particular the manual. Each module and each function now has its own dedicated manual page with full details and examples.
Compatibility Compatibility with Erlang/OTP R16, 17 and 18 has been dropped. Erlang/OTP 19.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.1 to 2.2</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.1/</guid>
      <description>Cowboy 2.2 focused on adding features required for writing gRPC servers and on completing test suites for the core HTTP RFCs, fixing many bugs along the way.
Features added Add support for sending trailers at the end of response bodies. Trailers are additional header fields that may be sent after the body to add more information to the response. Their usage is required in gRPC servers. They are optional and may be discarded in other scenarios (for example if the request goes through an HTTP/1.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.1 to 2.2</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.1/</guid>
      <description>Cowboy 2.2 focused on adding features required for writing gRPC servers and on completing test suites for the core HTTP RFCs, fixing many bugs along the way.
Features added Add support for sending trailers at the end of response bodies. Trailers are additional header fields that may be sent after the body to add more information to the response. Their usage is required in gRPC servers. They are optional and may be discarded in other scenarios (for example if the request goes through an HTTP/1.</description>
    </item>
    
    <item>
      <title>HTTP and other specifications</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/specs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/specs/</guid>
      <description>This chapter intends to list all the specification documents for or related to HTTP.
HTTP IANA Registries HTTP Method Registry  HTTP Status Code Registry  Message Headers  HTTP Parameters  HTTP Alt-Svc Parameter Registry  HTTP Authentication Scheme Registry  HTTP Cache Directive Registry  HTTP Digest Algorithm Values  HTTP Origin-Bound Authentication Device Identifier Types  HTTP Upgrade Token Registry  HTTP Warn Codes  HTTP/2 Parameters  WebSocket Protocol Registries   Current CORS: Cross-Origin Resource Sharing  CSP2: Content Security Policy Level 2  DNT: Tracking Preference Expression (DNT)  eventsource: Server-Sent Events  Form content types: Form content types  Preload: Preload  PROXY: The PROXY protocol  REST: Fielding&amp;apos;s Dissertation  RFC 1945: HTTP/1.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.0 to 2.1</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_2.0/</guid>
      <description>Cowboy 2.1 focused on adding features that were temporarily removed in Cowboy 2.0. A number of bugs found in the 2.0 release were also fixed.
Features added It is now possible to obtain the client TLS certificate and the local IP/port for the connection from the Req object.  Informational responses (1XX responses) can now be sent. They must be sent before initiating the final response.  The expect: 100-continue header is now handled automatically.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 2.0 to 2.1</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_2.0/</guid>
      <description>Cowboy 2.1 focused on adding features that were temporarily removed in Cowboy 2.0. A number of bugs found in the 2.0 release were also fixed.
Features added It is now possible to obtain the client TLS certificate and the local IP/port for the connection from the Req object.  Informational responses (1XX responses) can now be sent. They must be sent before initiating the final response.  The expect: 100-continue header is now handled automatically.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 1.0 to 2.0</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_1.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/migrating_from_1.0/</guid>
      <description>A lot has changed between Cowboy 1.0 and 2.0. The cowboy_req interface in particular has seen a massive revamp. Hooks are gone, their functionality can now be achieved via stream handlers.
The documentation has seen great work, in particular the manual. Each module and each function now has its own dedicated manual page with full details and examples.
Compatibility Compatibility with Erlang/OTP R16, 17 and 18 has been dropped. Erlang/OTP 19.</description>
    </item>
    
    <item>
      <title>Migrating from Cowboy 1.0 to 2.0</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_1.0/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/migrating_from_1.0/</guid>
      <description>A lot has changed between Cowboy 1.0 and 2.0. The cowboy_req interface in particular has seen a massive revamp. Hooks are gone, their functionality can now be achieved via stream handlers.
The documentation has seen great work, in particular the manual. Each module and each function now has its own dedicated manual page with full details and examples.
Compatibility Compatibility with Erlang/OTP R16, 17 and 18 has been dropped. Erlang/OTP 19.</description>
    </item>
    
    <item>
      <title>HTTP and other specifications</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/specs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/specs/</guid>
      <description>This chapter intends to list all the specification documents for or related to HTTP.
HTTP IANA Registries HTTP Method Registry  HTTP Status Code Registry  Message Headers  HTTP Parameters  HTTP Alt-Svc Parameter Registry  HTTP Authentication Scheme Registry  HTTP Cache Directive Registry  HTTP Digest Algorithm Values  HTTP Origin-Bound Authentication Device Identifier Types  HTTP Upgrade Token Registry  HTTP Warn Codes  HTTP/2 Parameters  WebSocket Protocol Registries   Current CORS: Cross-Origin Resource Sharing  CSP2: Content Security Policy Level 2  DNT: Tracking Preference Expression (DNT)  eventsource: Server-Sent Events  Form content types: Form content types  Preload: Preload  PROXY: The PROXY protocol  REST: Fielding&amp;apos;s Dissertation  RFC 1945: HTTP/1.</description>
    </item>
    
    <item>
      <title>HTTP and other specifications</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/specs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/specs/</guid>
      <description>This chapter intends to list all the specification documents for or related to HTTP.
HTTP IANA Registries HTTP Method Registry  HTTP Status Code Registry  Message Headers  HTTP Parameters  HTTP Alt-Svc Parameter Registry  HTTP Authentication Scheme Registry  HTTP Cache Directive Registry  HTTP Digest Algorithm Values  HTTP Origin-Bound Authentication Device Identifier Types  HTTP Upgrade Token Registry  HTTP Warn Codes  HTTP/2 Parameters  WebSocket Protocol Registries   Current CORS: Cross-Origin Resource Sharing  CSP2: Content Security Policy Level 2  DNT: Tracking Preference Expression (DNT)  eventsource: Server-Sent Events  Form content types: Form content types  Preload: Preload  PROXY: The PROXY protocol  REST: Fielding&amp;apos;s Dissertation  RFC 1945: HTTP/1.</description>
    </item>
    
    <item>
      <title>Merry Christmas 2019: New Beginnings</title>
      <link>https://ninenines.eu/articles/merry-christmas-2019/</link>
      <pubDate>Mon, 23 Dec 2019 07:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/merry-christmas-2019/</guid>
      <description>Hope everyone had a great year. Let&amp;apos;s take a look at what happened and what&amp;apos;s coming.
2019 has been the year of pre-releases with Ranch 2.0 and Gun 2.0 getting close to completion. I hope both of them will be out in the first half of 2020. They were supposed to be released in 2019, but I guess that was a bit optimistic. Ranch 2.0 is a big performance improvement if you need to quickly open a large amount of connections (but you probably don&amp;apos;t), while Gun 2.</description>
    </item>
    
    <item>
      <title>GitHub Sponsors</title>
      <link>https://ninenines.eu/articles/github-sponsors/</link>
      <pubDate>Mon, 28 Oct 2019 07:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/github-sponsors/</guid>
      <description>You can now reward my work via GitHub Sponsors.
GitHub will basically double the funds given to me for one year, so now&amp;apos;s the best time to reward my work!
I have replaced all BountySource links with GitHub Sponsors because GitHub Sponsors will make it easier for me to know who sponsors my work when responding to issues. We&amp;apos;ll see how that goes.
Head on to my GitHub Sponsors page now!</description>
    </item>
    
    <item>
      <title>Cowboy 2.7</title>
      <link>https://ninenines.eu/articles/cowboy-2.7.0/</link>
      <pubDate>Wed, 16 Oct 2019 07:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.7.0/</guid>
      <description>Cowboy 2.7.0 has been released!
Cowboy 2.7 improves the HTTP/2 code with optimizations around the sending of DATA and WINDOW_UPDATE frames; graceful shutdown of the connection when the client is going away; and rate limiting mechanisms. New options and mechanisms have also been added to control the amount of memory Cowboy ends up using with both HTTP/1.1 and HTTP/2. Much of this work was done to address HTTP/2 CVEs about potential denial of service.</description>
    </item>
    
    <item>
      <title>Gun 2.0 pre-release 1</title>
      <link>https://ninenines.eu/articles/gun-2.0.0-pre.1/</link>
      <pubDate>Fri, 27 Sep 2019 07:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/gun-2.0.0-pre.1/</guid>
      <description>Gun 2.0.0-pre.1 has been released!
The first pre-release version of Gun 2.0 has been released! Gun 2.0 adds a ton of features along with a small number of breaking changes.
Before listing the features please note that this pre-release includes a fix for a potential security vulnerability! This only applies when Gun is used inside a proxy under specific circumstances. Please see the migration guide for details. Since the issue also exists in the previous version I have released Gun 1.</description>
    </item>
    
    <item>
      <title>Erlang meetup: 10 septembre 2019</title>
      <link>https://ninenines.eu/articles/erlang-meetup-10-septembre-2019/</link>
      <pubDate>Thu, 22 Aug 2019 07:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/erlang-meetup-10-septembre-2019/</guid>
      <description>Erlang meetups are resuming and I will be present at the next one in Paris on the 10th of September. As the meetup and my talk about Gun will be in French the rest of this post will be in French as well. If you are around Paris that night, you are welcome to join and chat, even if you don&amp;apos;t speak the language!
Je serai au meetup Erlang le 10 septembre chez Datadog à Paris.</description>
    </item>
    
    <item>
      <title>Ranch 2.0 release candidate 1</title>
      <link>https://ninenines.eu/articles/ranch-2.0.0-rc.1/</link>
      <pubDate>Thu, 18 Jul 2019 07:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/ranch-2.0.0-rc.1/</guid>
      <description>Ranch 2.0.0-rc.1 has been released!
We are getting very close to releasing Ranch 2.0! As most of the tremendous programming work was done by contributor Jan Uhlig, I will yield the floor and let him describe what went into this great release.
In Ranch 1.x, there is only one supervisor per Ranch listener to start and manage connection processes. Under high load (many clients rapidly connecting and/or disconnecting), the message queue of this one supervisor could become congested, leading to declining accept rates or a stalled listener.</description>
    </item>
    
    <item>
      <title>Joe Armstrong the rubber duck</title>
      <link>https://ninenines.eu/articles/joe_the_rubber_duck/</link>
      <pubDate>Tue, 11 Jun 2019 07:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/joe_the_rubber_duck/</guid>
      <description>Joe Armstrong passed away a couple months ago. This was a sad day, completely unexpected to me, and he will be sorely missed.
Great eulogies were written.
My most striking memory of Joe was during dinner at his place after a conference in Stockholm many years ago. Joe was describing his rubber duck debugging method and introduced us to his famous rubber duck.
&amp;quot;When you can&amp;apos;t figure it out, ask the duck!</description>
    </item>
    
    <item>
      <title>Merry Christmas 2018: A Recap</title>
      <link>https://ninenines.eu/articles/merry-christmas-2018/</link>
      <pubDate>Tue, 25 Dec 2018 07:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/merry-christmas-2018/</guid>
      <description>As the year 2018 ends it&amp;apos;s time for a short recap and a look forward for the next year.
Overall, more than half of all open tickets have been closed. Most tickets were opened since 2015 and I couldn&amp;apos;t get to those, but now that pre-school started I have a lot more time! I&amp;apos;m aiming to keep the number of tickets below 100 across all my projects.
Cowboy 2.x is now mature.</description>
    </item>
    
    <item>
      <title>Cowboy 2.6</title>
      <link>https://ninenines.eu/articles/cowboy-2.6.0/</link>
      <pubDate>Mon, 19 Nov 2018 07:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.6.0/</guid>
      <description>Cowboy 2.6.0 has been released!
Cowboy 2.6 greatly refactored the HTTP/2 code, a large part of which was moved to Cowlib and is now used by both the Cowboy server and the Gun client.
A large number of tickets were also closed which resulted in many bugs fixed and many features and options added, although some of them are still experimental.
Of note is the support for the PROXY protocol header built directly into Cowboy; the ability to use the sendfile tuple to send files while streaming a response body (for example you could build a tar file on the fly); and experimental support for range requests in the REST and static file handlers, including an automatic mode that lets you enable byte range requests to existing handlers with what&amp;apos;s basically a one-liner.</description>
    </item>
    
    <item>
      <title>Ranch 1.7</title>
      <link>https://ninenines.eu/articles/ranch-1.7.0/</link>
      <pubDate>Wed, 14 Nov 2018 10:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/ranch-1.7.0/</guid>
      <description>Ranch 1.7.0 has been released!
This release adds built-in support for the PROXY protocol.
The PROXY protocol is a simple and efficient way for proxies to transmit information about the client.
While a third-party library already existed, it was not entirely compatible with the Ranch interface, in particular when socket active mode was involved. This new implementation fixes that and supports the full protocol with as little overhead as possible compared to normal operations: just one extra function call.</description>
    </item>
    
    <item>
      <title>Cowboy 2.5</title>
      <link>https://ninenines.eu/articles/cowboy-2.5.0/</link>
      <pubDate>Wed, 03 Oct 2018 07:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.5.0/</guid>
      <description>Cowboy 2.5.0 has been released!
Cowboy 2.5 focused on making the test suites pass. It is now possible to get all the Cowboy tests to pass successfully, at least on Linux and on the more recent Erlang/OTP versions.
HTTP/1.1 has been improved with a fix for the TCP reset problem and the ability to stream a response body without using chunked transfer-encoding.
Two functions have been added: cowboy_req:stream_events/3 encodes and streams one or more text/event-stream events, and cowboy_req:read_and_match_urlencoded_body/2,3 reads, parses and matches application/x-www-form-urlencoded request bodies.</description>
    </item>
    
    <item>
      <title>Gun 1.3</title>
      <link>https://ninenines.eu/articles/gun-1.3.0/</link>
      <pubDate>Mon, 01 Oct 2018 10:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/gun-1.3.0/</guid>
      <description>Gun 1.3.0 has been released!
Gun is an HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP.
This release improves the CONNECT support introduced in the previous version and adds built-in Websocket protocol negotiation.
A complete list of changes can be found in the migration guide: Migrating from Gun 1.2 to 1.3.
You can donate to this project via GitHub Sponsors. These funds are used to pay for additional servers for testing. And healthy food.</description>
    </item>
    
    <item>
      <title>Gun 1.2</title>
      <link>https://ninenines.eu/articles/gun-1.2.0/</link>
      <pubDate>Mon, 17 Sep 2018 10:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/gun-1.2.0/</guid>
      <description>Gun 1.2.0 has been released!
Gun is an HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP.
Gun now supports issuing CONNECT requests to HTTP proxies in order to establish tunnels to origin servers. Gun can establish tunnels over one or more proxies as necessary.
All existing protocols can be used inside the tunnel, including HTTP/1.1, HTTP/2 and Websocket over both TCP and TLS connections.
Note that it is currently not possible to tunnel a TLS connection via an HTTPS proxy due to limitations in the current version of Erlang/OTP.</description>
    </item>
    
    <item>
      <title>Ranch 1.6</title>
      <link>https://ninenines.eu/articles/ranch-1.6.0/</link>
      <pubDate>Wed, 01 Aug 2018 10:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/ranch-1.6.0/</guid>
      <description>Ranch 1.6.0 has been released!
This release sees the introduction of a suspend/resume mechanism for the listeners which makes the listener close the listening socket and stop accepting new connections. Existing connections continue uninterrupted.
This can be used to update the socket options of the listener, or to implement a graceful shutdown. To that end a function has also been added which allows waiting until connections reach a certain number.</description>
    </item>
    
    <item>
      <title>Gun 1.0</title>
      <link>https://ninenines.eu/articles/gun-1.0.0/</link>
      <pubDate>Fri, 27 Jul 2018 10:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/gun-1.0.0/</guid>
      <description>Gun 1.0.0 has been released!
Gun is an HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP.
Gun provides an asynchronous interface and will keep the connection open to the server, reconnecting as necessary.
Gun has existed for many years as the test client for Cowboy and is now mature enough to receive a proper version. Gun is battle tested by customers and other users but is not the most well tested client there is.</description>
    </item>
    
    <item>
      <title>Asciideck: Asciidoc for Erlang</title>
      <link>https://ninenines.eu/articles/asciideck/</link>
      <pubDate>Wed, 13 Jun 2018 07:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/asciideck/</guid>
      <description>Asciideck is a new project I have been working on in my spare time that implements an Asciidoc parser and translation of Asciidoc documents into various output formats.
The Asciideck parser returns an AST for the document. That AST can be further manipulated should it be necessary: for example you may need to rewrite some relative links if you are not keeping the same file directory structure as the original Asciidoc documents.</description>
    </item>
    
    <item>
      <title>Gun 1.0 release candidate 1</title>
      <link>https://ninenines.eu/articles/gun-1.0.0-rc.1/</link>
      <pubDate>Mon, 04 Jun 2018 10:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/gun-1.0.0-rc.1/</guid>
      <description>Gun 1.0.0-rc.1 has been released!
Gun is an HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP.
Gun provides an asynchronous interface and will keep the connection open to the server, reconnecting as necessary.
Gun has existed for many years as the test client for Cowboy and is now mature enough to receive a proper version. Gun is battle tested by customers and other users but is not the most well tested client there is.</description>
    </item>
    
    <item>
      <title>Cowboy 2.4</title>
      <link>https://ninenines.eu/articles/cowboy-2.4.0/</link>
      <pubDate>Wed, 02 May 2018 10:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.4.0/</guid>
      <description>Cowboy 2.4.0 has been released!
Numerous HTTP/2 options have been added to control the HTTP/2 SETTINGS and general behavior of HTTP/2 connections. The options for initial window sizes, maximum frame sizes or compression table sizes might be of interest for optimizing the performance of HTTP/2 connections.
Experimental support for Websocket over HTTP/2 was added. Note that browsers do not currently support it. The only browser with partial support is Google Chrome 67 (dev build) started with a specific flag.</description>
    </item>
    
    <item>
      <title>Cowboy 2.3</title>
      <link>https://ninenines.eu/articles/cowboy-2.3.0/</link>
      <pubDate>Wed, 04 Apr 2018 12:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.3.0/</guid>
      <description>Cowboy 2.3.0 has been released!
This release focused on adding support for the functions from the sys module for introspecting Cowboy processes.
Many bugs have also been fixed. A more complete list of changes can be found in the migration guide: Migrating from Cowboy 2.2 to 2.3.
You can donate to this project via GitHub Sponsors because I need to eat snacks when I write code. Thanks in advance!
As usual, feedback is appreciated, and issues should be reported by opening a ticket.</description>
    </item>
    
    <item>
      <title>Cowboy 2.2</title>
      <link>https://ninenines.eu/articles/cowboy-2.2.0/</link>
      <pubDate>Wed, 13 Dec 2017 12:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.2.0/</guid>
      <description>Cowboy 2.2.0 has been released!
This release focused on adding features required for writing gRPC servers and on completing test suites for the core HTTP RFCs.
The cowboy_req:stream_trailers/2 function has been added. It terminates the streamed response by adding some trailer field values. This feature is required for gRPC.  The max_skip_body_length option was added. It controls how much of the request body we are willing to skip to get to the next request for HTTP/1.</description>
    </item>
    
    <item>
      <title>Cowboy 2.1</title>
      <link>https://ninenines.eu/articles/cowboy-2.1.0/</link>
      <pubDate>Thu, 09 Nov 2017 12:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.1.0/</guid>
      <description>Cowboy 2.1.0 has been released!
This release focused on adding features that were temporarily removed during the 2.0 release process:
The client TLS certificate can now be obtained.  The 100 Continue response is now sent automatically again when necessary.  NEW: It is now possible to send informational responses (1XX) directly from user code via the cowboy_req:inform/2,3 functions.  NEW: cowboy_rest handlers can now switch to any other type of handler from almost any callback.</description>
    </item>
    
    <item>
      <title>Cowboy 2.0</title>
      <link>https://ninenines.eu/articles/cowboy-2.0.0/</link>
      <pubDate>Wed, 04 Oct 2017 12:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.0.0/</guid>
      <description>Cowboy 2.0.0 has been released!
This is the new stable version of Cowboy. There are no new releases planned for the 1.x version of Cowboy.
The highlights from the release are:
HTTP/2 support!  Websocket compression!  Much simpler, cleaner interface. No more weird errors just because you discard the Req object.  A new low-level interface that receives all events from every set of request and response. This replaces the awkward hooks from 1.</description>
    </item>
    
    <item>
      <title>Cowboy 2.0 release candidate 2</title>
      <link>https://ninenines.eu/articles/cowboy-2.0.0-rc.2/</link>
      <pubDate>Wed, 23 Aug 2017 18:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.0.0-rc.2/</guid>
      <description>Cowboy 2.0.0-rc.2 has been released!
This is the new recommended version of Cowboy. Its API should not change before release. While you probably should not use it in production yet, many do successfully. Use at your own risk.
This new version contains fixes for the following issues:
HTTP/2 server push was using the wrong header compression context.  HTTP/2 flow control could end up queueing data in the wrong order when resuming the sending of data.</description>
    </item>
    
    <item>
      <title>Cowboy 2.0 release candidate 1</title>
      <link>https://ninenines.eu/articles/cowboy-2.0.0-rc.1/</link>
      <pubDate>Mon, 24 Jul 2017 18:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.0.0-rc.1/</guid>
      <description>Cowboy 2.0.0-rc.1 has been released!
This is the new recommended version of Cowboy. Its API should not change before release. While you probably should not use it in production yet, many do successfully. Use at your own risk.
The plan is to have a new RC version every couple weeks until the summer ends or later if there are still blocking issues open. Only issues that can&amp;apos;t be fixed without making breaking changes to the interface may block the release.</description>
    </item>
    
    <item>
      <title>The elephant in the room</title>
      <link>https://ninenines.eu/articles/the-elephant-in-the-room/</link>
      <pubDate>Sun, 26 Mar 2017 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/the-elephant-in-the-room/</guid>
      <description>Have you ever tried telling someone why they should use Erlang? You boast the smaller code size, the auto healing mechanisms, the distribution and they seem really excited. They wonder why they never heard about Erlang before. And then you show them what the code looks like. All excitement goes away. The smiles disappear. Their face starts becoming really serious.
You lost them. You know you lost them. They comment on the syntax, or perhaps you do, already admitting defeat.</description>
    </item>
    
    <item>
      <title>Don&#39;t let it crash</title>
      <link>https://ninenines.eu/articles/dont-let-it-crash/</link>
      <pubDate>Sun, 22 Jan 2017 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/dont-let-it-crash/</guid>
      <description>We have a specific mindset when writing Erlang programs. We focus on the normal execution of the program and don&amp;apos;t handle most of the errors that may occur. We sometimes call this normal execution the happy path.
The general pattern behind writing only for the happy path, letting the VM catch errors (writing them to a log for future consumption) and then having a supervisor restart the processes that failed from a clean state, has a name.</description>
    </item>
    
    <item>
      <title>Cowboy 2.0 pre-release 4</title>
      <link>https://ninenines.eu/articles/cowboy-2.0.0-pre.4/</link>
      <pubDate>Tue, 03 Jan 2017 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.0.0-pre.4/</guid>
      <description>Cowboy 2.0.0-pre.4 has been released!
This is the new recommended version of Cowboy. While I would not recommend putting it in production just yet, I do recommend you start writing new applications with this Cowboy version.
The most significant changes in the pre-release are:
A new architecture: there now is one process per connection and one process per request. This was done because HTTP/2 allows running requests concurrently.  Stream handlers.</description>
    </item>
    
    <item>
      <title>Ranch 1.3</title>
      <link>https://ninenines.eu/articles/ranch-1.3/</link>
      <pubDate>Mon, 28 Nov 2016 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/ranch-1.3/</guid>
      <description>Ranch 1.3.0 has been released!
This release fixes a number of long standing issues and adds a small number of features:
The ssl application has been added to the list of dependencies. If you don&amp;apos;t need it, you can remove it automatically when fetching Ranch or when building the release. If you do need it, you will no longer have issues shutting down a node because of Ranch.
The ranch:info/0 and ranch:procs/2 can be used to retrieve information about Ranch&amp;apos;s state.</description>
    </item>
    
    <item>
      <title>Mailing list archived</title>
      <link>https://ninenines.eu/articles/ml-archives/</link>
      <pubDate>Mon, 29 Aug 2016 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/ml-archives/</guid>
      <description>The old mailing list archives have been added to the site, mainly for referencing purposes.
The mailing list has been shut down and all personal information has been deleted.
If you need help with a project, consider either opening a ticket on that project&amp;apos;s issues tracker or going through the community channels (erlang-questions, #ninenines or #erlang on Freenode).
Prefer tickets; often when people have issues it highlights an underlying problem in the project or its documentation.</description>
    </item>
    
    <item>
      <title>Website update</title>
      <link>https://ninenines.eu/articles/website-update/</link>
      <pubDate>Sat, 02 Apr 2016 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/website-update/</guid>
      <description>Last week-end I updated the Nine Nines website.
I switched to Hugo. The site is now built from Asciidoc documents. You probably saw me switch to Asciidoc for documentation this past year. This is the natural conclusion to that story. The great thing is that with a little bit of Makefile magic I can just copy the documentation files into Hugo and poof, they appear on the website.
I am very happy with that new setup.</description>
    </item>
    
    <item>
      <title>The Erlanger Playbook September 2015 Update</title>
      <link>https://ninenines.eu/articles/erlanger-playbook-september-2015-update/</link>
      <pubDate>Wed, 02 Sep 2015 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/erlanger-playbook-september-2015-update/</guid>
      <description>An update to The Erlanger Playbook is now available!
The Erlanger Playbook is a book about software development using Erlang. It currently covers all areas from the conception, design, the writing of code, documentation and tests.
The book is still a work in progress. Future topics will include refactoring, debugging and tracing, benchmarking, releases, community management (for open source projects).
This update fixes a number of things and adds two chapters: IOlists and Erlang building blocks.</description>
    </item>
    
    <item>
      <title>Consulting &amp; Training</title>
      <link>https://ninenines.eu/services/</link>
      <pubDate>Wed, 01 Jul 2015 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/services/</guid>
      <description>If you are interested by any of these opportunities, send me an email.
Consulting You can get me, Loïc Hoguin, author of Cowboy, to help you solve a problem or work on a particular project.
My area of expertise is Erlang; HTTP, Websocket and REST APIs; design and implementation of protocols; and messaging systems.
I can also be helpful with testing or code reviews.
I offer both hourly and daily rates:</description>
    </item>
    
    <item>
      <title>Documentation</title>
      <link>https://ninenines.eu/docs/</link>
      <pubDate>Wed, 01 Jul 2015 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/docs/</guid>
      <description>Contribute Do you have examples, tutorials, videos about one or more of my projects? I would happily include them on this page.
Send me an email with the details.</description>
    </item>
    
    <item>
      <title>Donate</title>
      <link>https://ninenines.eu/donate/</link>
      <pubDate>Wed, 01 Jul 2015 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/donate/</guid>
      <description>Like my work? Donate! Donate to Loïc Hoguin because his work on Cowboy, Ranch, Gun and Erlang.mk is fantastic:
Recurring payment options are also available via GitHub Sponsors. These funds are used to cover the recurring expenses like food, dedicated servers or domain names.</description>
    </item>
    
    <item>
      <title>Public talks</title>
      <link>https://ninenines.eu/talks/</link>
      <pubDate>Wed, 01 Jul 2015 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/talks/</guid>
      <description>Talk requests Organizing a conference and in need of a speaker for a talk about Erlang and the Web? Need an introduction to Erlang/OTP for your company? Looking for a cool subject for a user group meeting?
Send me an email with the details.</description>
    </item>
    
    <item>
      <title>Slogan</title>
      <link>https://ninenines.eu/slogan/</link>
      <pubDate>Wed, 01 Jul 2015 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/slogan/</guid>
      <description>Reward my work via GitHub Sponsors andGitHub will double the funds I receive!</description>
    </item>
    
    <item>
      <title>The Erlanger Playbook</title>
      <link>https://ninenines.eu/articles/erlanger-playbook/</link>
      <pubDate>Thu, 18 Jun 2015 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/erlanger-playbook/</guid>
      <description>I am proud to announce the pre-release of The Erlanger Playbook.
The Erlanger Playbook is a book about software development using Erlang. It currently covers all areas from the conception, design, the writing of code, documentation and tests.
The book is still a work in progress. Future topics will include refactoring, debugging and tracing, benchmarking, releases, community management (for open source projects).
The following sections are currently available:
About this book; Changelog; Future additions  Erlang: Building blocks; Patterns  Workflow: Think; Write; Stay productive  Documentation: On documentation; Tutorials; User guide; Manual; README files  Design: RESTful APIs; Lessons learned  Code: Starting a project; Version control; Project structure; Code style; Best practices; Special processes; IOLists; The process dictionary  Tests: On testing; Success typing analysis; Manual testing; Unit testing; Functional testing  Selling Erlang: On persuasion; Don&amp;apos;t let it crash   Read a preview: Special processes</description>
    </item>
    
    <item>
      <title>Validating UTF-8 binaries with Erlang</title>
      <link>https://ninenines.eu/articles/erlang-validate-utf8/</link>
      <pubDate>Fri, 06 Mar 2015 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/erlang-validate-utf8/</guid>
      <description>Yesterday I pushed Websocket permessage-deflate to Cowboy master. I also pushed a change in the way the code validates UTF-8 data (required for text and close frames as per the spec).
When looking into why the permessage-deflate tests in autobahntestsuite were taking such a long time, I found that autobahn is using an adaptation of the algorithm named Flexible and Economical UTF-8 Decoder. This is the C99 implementation:
// Copyright (c) 2008-2009 Bjoern Hoehrmann &amp;lt;bjoern@hoehrmann.</description>
    </item>
    
    <item>
      <title>On open source</title>
      <link>https://ninenines.eu/articles/on-open-source/</link>
      <pubDate>Fri, 05 Sep 2014 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/on-open-source/</guid>
      <description>Last week I read a great article on contributing to open source by Alvaro Videla. He makes many great points and I am in agreement with most of it. This made me want to properly explain my point of view with regard to open source and contributions. Unlike most open source evangelism articles I will not talk about ideals or any of that crap, but rather my personal feelings and experience.</description>
    </item>
    
    <item>
      <title>The story so far</title>
      <link>https://ninenines.eu/articles/the-story-so-far/</link>
      <pubDate>Sat, 23 Aug 2014 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/the-story-so-far/</guid>
      <description>As I am away from home with little to do (some call this a vacation) I wanted to reflect a little on the story so far, or how I arrived to Erlang and got to where I am now. The raw personal experience. It&amp;apos;ll be an article that&amp;apos;s more about social aspect, communities and marketing a project than technical considerations. As a period piece, it will also allow me to reflect on the evolution of Erlang in recent years.</description>
    </item>
    
    <item>
      <title>Cowboy 2.0 and query strings</title>
      <link>https://ninenines.eu/articles/cowboy2-qs/</link>
      <pubDate>Wed, 20 Aug 2014 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy2-qs/</guid>
      <description>Now that Cowboy 1.0 is out, I can spend some of my time thinking about Cowboy 2.0 that will be released soon after Erlang/OTP 18.0. This entry discusses the proposed changes to query string handling in Cowboy.
Cowboy 2.0 will respond to user wishes by simplifying the interface of the cowboy_req module. Users want two things: less juggling with the Req variable, and more maps. Maps is the only dynamic key/value data structure in Erlang that we can match directly to extract values, allowing users to greatly simplify their code as they don&amp;apos;t need to call functions to do everything anymore.</description>
    </item>
    
    <item>
      <title>January 2014 status</title>
      <link>https://ninenines.eu/articles/january-2014-status/</link>
      <pubDate>Tue, 07 Jan 2014 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/january-2014-status/</guid>
      <description>I will now be regularly writing posts about project status, plans and hopes for the future.
Before that though, there&amp;apos;s one important news to share.
Until a year ago all development was financed through consulting and development services. This worked alright but too much time was spent doing things that didn&amp;apos;t benefit the open source projects. And that didn&amp;apos;t make me happy at all. Because I like being happy I stopped that for the most part and spent the year figuring things out, experimenting and discussing with people about it.</description>
    </item>
    
    <item>
      <title>Farwest got funded!</title>
      <link>https://ninenines.eu/articles/farwest-funded/</link>
      <pubDate>Thu, 27 Jun 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/farwest-funded/</guid>
      <description>This was a triumph! I&amp;apos;m making a note here: HUGE SUCCESS!!
It&amp;apos;s hard to overstate my satisfaction. Thanks to everyone who made this possible.
If you have backed this fundraiser, and haven&amp;apos;t provided your personal details yet, please do so quickly so that your rewards can be sent!
I am hoping that we will be able to make good use of all that money. The details of the expenses will be published regularly on the 2013 Fundraiser wiki page, giving you full disclosure as to how your money is used.</description>
    </item>
    
    <item>
      <title>Build Erlang releases with Erlang.mk and Relx</title>
      <link>https://ninenines.eu/articles/erlang.mk-and-relx/</link>
      <pubDate>Tue, 28 May 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/erlang.mk-and-relx/</guid>
      <description>Building OTP releases has always been a difficult task. Tools like Reltool or Rebar have made this simpler, but it&amp;apos;s no panacea. This article will show you an alternative and hopefully much simpler solution.
There is two steps to building a release. First you need to build the various OTP applications you want to include in the release. Once done, you need to create the release itself, by including the Erlang runtime system alongside the applications, a boot script to start the node and all its applications, and some configuration files.</description>
    </item>
    
    <item>
      <title>Xerl: intermediate module</title>
      <link>https://ninenines.eu/articles/xerl-0.5-intermediate-module/</link>
      <pubDate>Mon, 25 Mar 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/xerl-0.5-intermediate-module/</guid>
      <description>Today we will start the work on the intermediate module that will be used to run the code for the expressions found in our file&amp;apos;s body, replacing our interpreter.
This is what we want to have when all the work is done:
xerl -&amp;gt; tokens -&amp;gt; AST -&amp;gt; intermediate -&amp;gt; cerl Today we will perform this work only on the atomic integer expression however, so we will not build any module at the end.</description>
    </item>
    
    <item>
      <title>Xerl: expression separator</title>
      <link>https://ninenines.eu/articles/xerl-0.4-expression-separator/</link>
      <pubDate>Fri, 01 Mar 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/xerl-0.4-expression-separator/</guid>
      <description>As promised we are adding an expression separator this time. This will be short and easy.
In the tokenizer we only need to add a line recognizing the comma as a valid token.
, : {token, {&#39;,&#39;, TokenLine}}.  Then we need to change the following lines in the parser:
exprs -&amp;gt; expr : [&#39;$1&#39;]. exprs -&amp;gt; expr exprs : [&#39;$1&#39; | &#39;$2&#39;].  And add a comma between the expressions on the second line:</description>
    </item>
    
    <item>
      <title>Erlang Scalability</title>
      <link>https://ninenines.eu/articles/erlang-scalability/</link>
      <pubDate>Mon, 18 Feb 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/erlang-scalability/</guid>
      <description>I would like to share some experience and theories on Erlang scalability.
This will be in the form of a series of hints, which may or may not be accompanied with explanations as to why things are this way, or how they improve or reduce the scalability of a system. I will try to do my best to avoid giving falsehoods, even if that means a few things won&amp;apos;t be explained.</description>
    </item>
    
    <item>
      <title>Xerl: atomic expressions</title>
      <link>https://ninenines.eu/articles/xerl-0.3-atomic-expressions/</link>
      <pubDate>Mon, 18 Feb 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/xerl-0.3-atomic-expressions/</guid>
      <description>We will be adding atomic integer expressions to our language. These look as follow in Erlang:
42.  And the result of this expression is of course 42.
We will be running this expression at compile time, since we don&amp;apos;t have the means to run code at runtime yet. This will of course result in no module being compiled, but that&amp;apos;s OK, it will allow us to discuss a few important things we&amp;apos;ll have to plan for later on.</description>
    </item>
    
    <item>
      <title>Xerl: two modules</title>
      <link>https://ninenines.eu/articles/xerl-0.2-two-modules/</link>
      <pubDate>Sun, 03 Feb 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/xerl-0.2-two-modules/</guid>
      <description>Everything is an expression.
This sentence carries profound meaning. We will invoke it many times over the course of these articles.
If everything is an expression, then the language shouldn&amp;apos;t have any problem with me defining two modules in the same source file.
mod first_module begin end mod second_module begin end  Likewise, it shouldn&amp;apos;t have any problem with me defining a module inside another module.
mod out_module begin mod in_module begin end end  Of course, in the context of the Erlang VM, these two snippets are equivalent; there is nothing preventing you from calling the in_module module from any other module.</description>
    </item>
    
    <item>
      <title>Xerl: empty modules</title>
      <link>https://ninenines.eu/articles/xerl-0.1-empty-modules/</link>
      <pubDate>Wed, 30 Jan 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/xerl-0.1-empty-modules/</guid>
      <description>Let&amp;apos;s build a programming language. I call it Xerl: eXtended ERLang. It&amp;apos;ll be an occasion for us to learn a few things, especially me.
Unlike in Erlang, in this language, everything is an expression. This means that modules and functions are expression, and indeed that you can have more than one module per file.
We are just starting, so let&amp;apos;s no go ahead of ourselves here. We&amp;apos;ll begin with writing the code allowing us to compile an empty module.</description>
    </item>
    
    <item>
      <title>Build an FTP Server with Ranch in 30 Minutes</title>
      <link>https://ninenines.eu/articles/ranch-ftp/</link>
      <pubDate>Wed, 14 Nov 2012 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/ranch-ftp/</guid>
      <description>Last week I was speaking at the London Erlang Factory Lite where I presented a live demonstration of building an FTP server using Ranch. As there was no slide, you should use this article as a reference instead.
The goal of this article is to showcase how to use Ranch for writing a network protocol implementation, how Ranch gets out of the way to let you write the code that matters, and the common techniques used when writing servers.</description>
    </item>
    
    <item>
      <title>Erlang Tic Tac Toe</title>
      <link>https://ninenines.eu/articles/tictactoe/</link>
      <pubDate>Wed, 17 Oct 2012 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/tictactoe/</guid>
      <description>Everyone knows Tic Tac Toe, right?
Players choose either to be the Xs or the Os, then place their symbol on a 3x3 board one after another, trying to create a line of 3 of them.
Writing an algorithm to check for victory sounds easy, right? It&amp;apos;s easily tested, considering there&amp;apos;s only 8 possible winning rows (3 horizontal, 3 vertical and 2 diagonal).
In Erlang though, you probably wouldn&amp;apos;t want an algorithm.</description>
    </item>
    
    <item>
      <title>cow_cookie(3)</title>
      <link>https://ninenines.eu/docs/en/cowlib/2.8/manual/cow_cookie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowlib/2.8/manual/cow_cookie/</guid>
      <description>Name cow_cookie - Cookies
Description The module cow_cookie provides functions for parsing and manipulating cookie headers.
Exports cow_cookie:parse_cookie(3) - Parse a cookie header  cow_cookie:setcookie(3) - Generate a set-cookie header   Types cookie_opts() cookie_opts() :: #{ domain =&amp;gt; binary(), http_only =&amp;gt; boolean(), max_age =&amp;gt; non_neg_integer(), path =&amp;gt; binary(), same_site =&amp;gt; lax | strict, secure =&amp;gt; boolean() }  Options for the set-cookie header. They are added to the header as attributes.</description>
    </item>
    
    <item>
      <title>cow_cookie:parse_cookie(3)</title>
      <link>https://ninenines.eu/docs/en/cowlib/2.8/manual/cow_cookie.parse_cookie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowlib/2.8/manual/cow_cookie.parse_cookie/</guid>
      <description>Name cow_cookie:parse_cookie - Parse a cookie header
Description parse_cookie(Cookie :: binary()) -&amp;gt; [{binary(), binary()}]  Parse a cookie header.
Arguments Cookie The cookie header value.
  Return value A list of cookie name/value pairs is returned on success.
An exception is thrown in the event of a parse error.
Changelog 1.0: Function introduced.   Examples Parse a cookie header Cookies = cow_cookie:parse_cookie(CookieHd).  See also cow_cookie(3), cow_cookie:setcookie(3)</description>
    </item>
    
    <item>
      <title>cow_cookie:setcookie(3)</title>
      <link>https://ninenines.eu/docs/en/cowlib/2.8/manual/cow_cookie.setcookie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowlib/2.8/manual/cow_cookie.setcookie/</guid>
      <description>Name cow_cookie:setcookie - Generate a set-cookie header
Description setcookie(Name :: iodata(), Value :: iodata(), Opts :: cow_cookie:cookie_opts()) -&amp;gt; iolist()  Generate a set-cookie header.
Arguments Name Cookie name.
 Value Cookie value.
 Opts Options added to the set-cookie header as attributes.
  Return value An iolist with the generated set-cookie header value.
Changelog 1.0: Function introduced.   Examples Generate a set-cookie header SetCookie = cow_cookie:setcookie(&amp;lt;&amp;lt;&#34;sessionid&#34;&amp;gt;&amp;gt;, ID, #{ http_only =&amp;gt; true, secure =&amp;gt; true }).</description>
    </item>
    
    <item>
      <title>Cowboy Function Reference</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/</guid>
      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
Modules Functions:
cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
    </item>
    
    <item>
      <title>Cowboy Function Reference</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/</guid>
      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
Modules Functions:
cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
    </item>
    
    <item>
      <title>Cowboy Function Reference</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/</guid>
      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
Modules Functions:
cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
    </item>
    
    <item>
      <title>Cowboy Function Reference</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/</guid>
      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
Modules Functions:
cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
    </item>
    
    <item>
      <title>Cowboy Function Reference</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/</guid>
      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
Modules Functions:
cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
    </item>
    
    <item>
      <title>Cowboy Function Reference</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/</guid>
      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
Modules Functions:
cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
    </item>
    
    <item>
      <title>Cowboy User Guide</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/guide/</guid>
      <description>Rationale The modern Web  Erlang and the Web   Introduction Introduction  Getting started  Flow diagram   Configuration Listeners  Routing  Constraints   Handlers Handlers  Loop handlers  Static files   Request and response Request details  Reading the request body  Sending a response  Using cookies  Multipart   REST REST principles  Handling REST requests  REST flowcharts  Designing a resource handler   Websocket The Websocket protocol  Websocket handlers   Advanced Streams  Middlewares   Additional information Changes since Cowboy 2.</description>
    </item>
    
    <item>
      <title>Cowboy User Guide</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/guide/</guid>
      <description>Rationale The modern Web  Erlang and the Web   Introduction Introduction  Getting started  Flow diagram   Configuration Listeners  Routing  Constraints   Handlers Handlers  Loop handlers  Static files   Request and response Request details  Reading the request body  Sending a response  Using cookies  Multipart   REST REST principles  Handling REST requests  REST flowcharts  Designing a resource handler   Websocket The Websocket protocol  Websocket handlers   Advanced Streams  Middlewares   Additional information Migrating from Cowboy 2.</description>
    </item>
    
    <item>
      <title>Cowboy User Guide</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/guide/</guid>
      <description>Rationale The modern Web  Erlang and the Web   Introduction Introduction  Getting started  Flow diagram   Configuration Listeners  Routing  Constraints   Handlers Handlers  Loop handlers  Static files   Request and response Request details  Reading the request body  Sending a response  Using cookies  Multipart   REST REST principles  Handling REST requests  REST flowcharts  Designing a resource handler   Websocket The Websocket protocol  Websocket handlers   Advanced Streams  Middlewares   Additional information Migrating from Cowboy 2.</description>
    </item>
    
    <item>
      <title>Cowboy User Guide</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/guide/</guid>
      <description>Rationale The modern Web  Erlang and the Web   Introduction Introduction  Getting started  Flow diagram   Configuration Listeners  Routing  Constraints   Handlers Handlers  Loop handlers  Static files   Request and response Request details  Reading the request body  Sending a response  Using cookies  Multipart   REST REST principles  Handling REST requests  REST flowcharts  Designing a resource handler   Websocket The Websocket protocol  Websocket handlers   Advanced Streams  Middlewares   Additional information Migrating from Cowboy 2.</description>
    </item>
    
    <item>
      <title>Cowboy User Guide</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/guide/</guid>
      <description>Rationale The modern Web  Erlang and the Web   Introduction Introduction  Getting started  Flow diagram   Configuration Listeners  Routing  Constraints   Handlers Handlers  Loop handlers  Static files   Request and response Request details  Reading the request body  Sending a response  Using cookies  Multipart   REST REST principles  Handling REST requests  REST flowcharts  Designing a resource handler   Websocket The Websocket protocol  Websocket handlers   Advanced Streams  Middlewares   Additional information Changes since Cowboy 2.</description>
    </item>
    
    <item>
      <title>Cowboy User Guide</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/guide/</guid>
      <description>Rationale The modern Web  Erlang and the Web   Introduction Introduction  Getting started  Flow diagram   Configuration Listeners  Routing  Constraints   Handlers Handlers  Loop handlers  Static files   Request and response Request details  Reading the request body  Sending a response  Using cookies  Multipart   REST REST principles  Handling REST requests  REST flowcharts  Designing a resource handler   Websocket The Websocket protocol  Websocket handlers   Advanced Streams  Middlewares   Additional information Migrating from Cowboy 2.</description>
    </item>
    
    <item>
      <title>cowboy(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy/</guid>
      <description>Name cowboy - HTTP server
Description The module cowboy provides convenience functions for manipulating Ranch listeners.
Exports cowboy:start_clear(3) - Listen for connections using plain TCP  cowboy:start_tls(3) - Listen for connections using TLS  cowboy:stop_listener(3) - Stop the given listener  cowboy:set_env(3) - Update a listener&amp;apos;s environment value   Types fields() fields() :: [Name | {Name, Constraints} | {Name, Constraints, Default}] Name :: atom() Constraints :: Constraint | [Constraint] Constraint :: cowboy_constraints:constraint() Default :: any()  Fields description for match operations.</description>
    </item>
    
    <item>
      <title>cowboy(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy/</guid>
      <description>Name cowboy - HTTP server
Description The module cowboy provides convenience functions for manipulating Ranch listeners.
Exports cowboy:start_clear(3) - Listen for connections using plain TCP  cowboy:start_tls(3) - Listen for connections using TLS  cowboy:stop_listener(3) - Stop the given listener  cowboy:set_env(3) - Update a listener&amp;apos;s environment value   Types fields() fields() :: [Name | {Name, Constraints} | {Name, Constraints, Default}] Name :: atom() Constraints :: Constraint | [Constraint] Constraint :: cowboy_constraints:constraint() Default :: any()  Fields description for match operations.</description>
    </item>
    
    <item>
      <title>cowboy(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy/</guid>
      <description>Name cowboy - HTTP server
Description The module cowboy provides convenience functions for manipulating Ranch listeners.
Exports cowboy:start_clear(3) - Listen for connections using plain TCP  cowboy:start_tls(3) - Listen for connections using TLS  cowboy:stop_listener(3) - Stop the given listener  cowboy:set_env(3) - Update a listener&amp;apos;s environment value   Types fields() fields() :: [Name | {Name, Constraints} | {Name, Constraints, Default}] Name :: atom() Constraints :: Constraint | [Constraint] Constraint :: cowboy_constraints:constraint() Default :: any()  Fields description for match operations.</description>
    </item>
    
    <item>
      <title>cowboy(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy/</guid>
      <description>Name cowboy - HTTP server
Description The module cowboy provides convenience functions for manipulating Ranch listeners.
Exports cowboy:start_clear(3) - Listen for connections using plain TCP  cowboy:start_tls(3) - Listen for connections using TLS  cowboy:stop_listener(3) - Stop the given listener  cowboy:set_env(3) - Update a listener&amp;apos;s environment value   Types fields() fields() :: [Name | {Name, Constraints} | {Name, Constraints, Default}] Name :: atom() Constraints :: Constraint | [Constraint] Constraint :: cowboy_constraints:constraint() Default :: any()  Fields description for match operations.</description>
    </item>
    
    <item>
      <title>cowboy(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy/</guid>
      <description>Name cowboy - HTTP server
Description The module cowboy provides convenience functions for manipulating Ranch listeners.
Exports cowboy:start_clear(3) - Listen for connections using plain TCP  cowboy:start_tls(3) - Listen for connections using TLS  cowboy:stop_listener(3) - Stop the given listener  cowboy:set_env(3) - Update a listener&amp;apos;s environment value   Types fields() fields() :: [Name | {Name, Constraints} | {Name, Constraints, Default}] Name :: atom() Constraints :: Constraint | [Constraint] Constraint :: cowboy_constraints:constraint() Default :: any()  Fields description for match operations.</description>
    </item>
    
    <item>
      <title>cowboy(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy/</guid>
      <description>Name cowboy - HTTP server
Description The module cowboy provides convenience functions for manipulating Ranch listeners.
Exports cowboy:start_clear(3) - Listen for connections using plain TCP  cowboy:start_tls(3) - Listen for connections using TLS  cowboy:stop_listener(3) - Stop the given listener  cowboy:set_env(3) - Update a listener&amp;apos;s environment value   Types fields() fields() :: [Name | {Name, Constraints} | {Name, Constraints, Default}] Name :: atom() Constraints :: Constraint | [Constraint] Constraint :: cowboy_constraints:constraint() Default :: any()  Fields description for match operations.</description>
    </item>
    
    <item>
      <title>cowboy(7)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_app/</guid>
      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
Modules Functions:
cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
    </item>
    
    <item>
      <title>cowboy(7)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_app/</guid>
      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
Modules Functions:
cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
    </item>
    
    <item>
      <title>cowboy(7)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_app/</guid>
      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
Modules Functions:
cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
    </item>
    
    <item>
      <title>cowboy(7)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_app/</guid>
      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
Modules Functions:
cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
    </item>
    
    <item>
      <title>cowboy(7)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_app/</guid>
      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
Modules Functions:
cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
    </item>
    
    <item>
      <title>cowboy(7)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_app/</guid>
      <description>Name cowboy - Small, fast, modern HTTP server for Erlang/OTP
Description Cowboy is an HTTP server for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Cowboy aims to provide a complete HTTP stack. This includes the implementation of the HTTP RFCs but also any directly related standards, like Websocket or Server-Sent Events.
Modules Functions:
cowboy(3) - Listener management  cowboy_req(3) - Request and response  cowboy_router(3) - Router  cowboy_constraints(3) - Constraints   Protocols:</description>
    </item>
    
    <item>
      <title>cowboy:set_env(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy.set_env/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy.set_env/</guid>
      <description>Name cowboy:set_env - Update a listener&amp;apos;s environment value
Description set_env(Name :: ranch:ref(), Key :: atom(), Value :: any()) -&amp;gt; ok  Set or update an environment value for a previously started listener.
This is most useful for updating the routes dynamically, without having to restart the listener.
The new value will only be available to new connections. Pre-existing connections will still use the old value.
Arguments Name The name of the listener to update.</description>
    </item>
    
    <item>
      <title>cowboy:set_env(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy.set_env/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy.set_env/</guid>
      <description>Name cowboy:set_env - Update a listener&amp;apos;s environment value
Description set_env(Name :: ranch:ref(), Key :: atom(), Value :: any()) -&amp;gt; ok  Set or update an environment value for a previously started listener.
This is most useful for updating the routes dynamically, without having to restart the listener.
The new value will only be available to new connections. Pre-existing connections will still use the old value.
Arguments Name The name of the listener to update.</description>
    </item>
    
    <item>
      <title>cowboy:set_env(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy.set_env/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy.set_env/</guid>
      <description>Name cowboy:set_env - Update a listener&amp;apos;s environment value
Description set_env(Name :: ranch:ref(), Key :: atom(), Value :: any()) -&amp;gt; ok  Set or update an environment value for a previously started listener.
This is most useful for updating the routes dynamically, without having to restart the listener.
The new value will only be available to new connections. Pre-existing connections will still use the old value.
Arguments Name The name of the listener to update.</description>
    </item>
    
    <item>
      <title>cowboy:set_env(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy.set_env/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy.set_env/</guid>
      <description>Name cowboy:set_env - Update a listener&amp;apos;s environment value
Description set_env(Name :: ranch:ref(), Key :: atom(), Value :: any()) -&amp;gt; ok  Set or update an environment value for a previously started listener.
This is most useful for updating the routes dynamically, without having to restart the listener.
The new value will only be available to new connections. Pre-existing connections will still use the old value.
Arguments Name The name of the listener to update.</description>
    </item>
    
    <item>
      <title>cowboy:set_env(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy.set_env/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy.set_env/</guid>
      <description>Name cowboy:set_env - Update a listener&amp;apos;s environment value
Description set_env(Name :: ranch:ref(), Key :: atom(), Value :: any()) -&amp;gt; ok  Set or update an environment value for a previously started listener.
This is most useful for updating the routes dynamically, without having to restart the listener.
The new value will only be available to new connections. Pre-existing connections will still use the old value.
Arguments Name The name of the listener to update.</description>
    </item>
    
    <item>
      <title>cowboy:set_env(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy.set_env/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy.set_env/</guid>
      <description>Name cowboy:set_env - Update a listener&amp;apos;s environment value
Description set_env(Name :: ranch:ref(), Key :: atom(), Value :: any()) -&amp;gt; ok  Set or update an environment value for a previously started listener.
This is most useful for updating the routes dynamically, without having to restart the listener.
The new value will only be available to new connections. Pre-existing connections will still use the old value.
Arguments Name The name of the listener to update.</description>
    </item>
    
    <item>
      <title>cowboy:start_clear(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy.start_clear/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy.start_clear/</guid>
      <description>Name cowboy:start_clear - Listen for connections using plain TCP
Description start_clear(Name :: ranch:ref(), TransportOpts :: ranch_tcp:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a clear TCP channel.
Both HTTP/1.1 and HTTP/2 are supported on this listener. HTTP/2 has two methods of establishing a connection over a clear TCP channel. Both the upgrade and the prior knowledge methods are supported.
Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
    </item>
    
    <item>
      <title>cowboy:start_clear(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy.start_clear/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy.start_clear/</guid>
      <description>Name cowboy:start_clear - Listen for connections using plain TCP
Description start_clear(Name :: ranch:ref(), TransportOpts :: ranch_tcp:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a clear TCP channel.
Both HTTP/1.1 and HTTP/2 are supported on this listener. HTTP/2 has two methods of establishing a connection over a clear TCP channel. Both the upgrade and the prior knowledge methods are supported.
Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
    </item>
    
    <item>
      <title>cowboy:start_clear(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy.start_clear/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy.start_clear/</guid>
      <description>Name cowboy:start_clear - Listen for connections using plain TCP
Description start_clear(Name :: ranch:ref(), TransportOpts :: ranch_tcp:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a clear TCP channel.
Both HTTP/1.1 and HTTP/2 are supported on this listener. HTTP/2 has two methods of establishing a connection over a clear TCP channel. Both the upgrade and the prior knowledge methods are supported.
Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
    </item>
    
    <item>
      <title>cowboy:start_clear(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy.start_clear/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy.start_clear/</guid>
      <description>Name cowboy:start_clear - Listen for connections using plain TCP
Description start_clear(Name :: ranch:ref(), TransportOpts :: ranch_tcp:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a clear TCP channel.
Both HTTP/1.1 and HTTP/2 are supported on this listener. HTTP/2 has two methods of establishing a connection over a clear TCP channel. Both the upgrade and the prior knowledge methods are supported.
Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
    </item>
    
    <item>
      <title>cowboy:start_clear(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy.start_clear/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy.start_clear/</guid>
      <description>Name cowboy:start_clear - Listen for connections using plain TCP
Description start_clear(Name :: ranch:ref(), TransportOpts :: ranch_tcp:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a clear TCP channel.
Both HTTP/1.1 and HTTP/2 are supported on this listener. HTTP/2 has two methods of establishing a connection over a clear TCP channel. Both the upgrade and the prior knowledge methods are supported.
Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
    </item>
    
    <item>
      <title>cowboy:start_clear(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy.start_clear/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy.start_clear/</guid>
      <description>Name cowboy:start_clear - Listen for connections using plain TCP
Description start_clear(Name :: ranch:ref(), TransportOpts :: ranch_tcp:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a clear TCP channel.
Both HTTP/1.1 and HTTP/2 are supported on this listener. HTTP/2 has two methods of establishing a connection over a clear TCP channel. Both the upgrade and the prior knowledge methods are supported.
Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
    </item>
    
    <item>
      <title>cowboy:start_tls(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy.start_tls/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy.start_tls/</guid>
      <description>Name cowboy:start_tls - Listen for connections using TLS
Description start_tls(Name :: ranch:ref(), TransportOpts :: ranch_ssl:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a secure TLS channel.
Both HTTP/1.1 and HTTP/2 are supported on this listener. The ALPN TLS extension must be used to initiate an HTTP/2 connection.
Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
    </item>
    
    <item>
      <title>cowboy:start_tls(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy.start_tls/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy.start_tls/</guid>
      <description>Name cowboy:start_tls - Listen for connections using TLS
Description start_tls(Name :: ranch:ref(), TransportOpts :: ranch_ssl:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a secure TLS channel.
Both HTTP/1.1 and HTTP/2 are supported on this listener. The ALPN TLS extension must be used to initiate an HTTP/2 connection.
Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
    </item>
    
    <item>
      <title>cowboy:start_tls(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy.start_tls/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy.start_tls/</guid>
      <description>Name cowboy:start_tls - Listen for connections using TLS
Description start_tls(Name :: ranch:ref(), TransportOpts :: ranch_ssl:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a secure TLS channel.
Both HTTP/1.1 and HTTP/2 are supported on this listener. The ALPN TLS extension must be used to initiate an HTTP/2 connection.
Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
    </item>
    
    <item>
      <title>cowboy:start_tls(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy.start_tls/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy.start_tls/</guid>
      <description>Name cowboy:start_tls - Listen for connections using TLS
Description start_tls(Name :: ranch:ref(), TransportOpts :: ranch_ssl:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a secure TLS channel.
Both HTTP/1.1 and HTTP/2 are supported on this listener. The ALPN TLS extension must be used to initiate an HTTP/2 connection.
Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
    </item>
    
    <item>
      <title>cowboy:start_tls(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy.start_tls/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy.start_tls/</guid>
      <description>Name cowboy:start_tls - Listen for connections using TLS
Description start_tls(Name :: ranch:ref(), TransportOpts :: ranch_ssl:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a secure TLS channel.
Both HTTP/1.1 and HTTP/2 are supported on this listener. The ALPN TLS extension must be used to initiate an HTTP/2 connection.
Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
    </item>
    
    <item>
      <title>cowboy:start_tls(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy.start_tls/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy.start_tls/</guid>
      <description>Name cowboy:start_tls - Listen for connections using TLS
Description start_tls(Name :: ranch:ref(), TransportOpts :: ranch_ssl:opts(), ProtocolOpts :: opts()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start listening for connections over a secure TLS channel.
Both HTTP/1.1 and HTTP/2 are supported on this listener. The ALPN TLS extension must be used to initiate an HTTP/2 connection.
Arguments Name The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the routes defined.</description>
    </item>
    
    <item>
      <title>cowboy:stop_listener(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy.stop_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy.stop_listener/</guid>
      <description>Name cowboy:stop_listener - Stop the given listener
Description stop_listener(Name :: ranch:ref()) -&amp;gt; ok | {error, not_found}.  Stop a previously started listener.
Alias of ranch:stop_listener(3).
Arguments Name The name of the listener to be stopped.
The name of the listener is the first argument given to the cowboy:start_clear(3), cowboy:start_tls(3) or ranch:start_listener(3) function.
  Return value The atom ok is returned on success.
The {error, not_found} tuple is returned when the listener does not exist.</description>
    </item>
    
    <item>
      <title>cowboy:stop_listener(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy.stop_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy.stop_listener/</guid>
      <description>Name cowboy:stop_listener - Stop the given listener
Description stop_listener(Name :: ranch:ref()) -&amp;gt; ok | {error, not_found}.  Stop a previously started listener.
Alias of ranch:stop_listener(3).
Arguments Name The name of the listener to be stopped.
The name of the listener is the first argument given to the cowboy:start_clear(3), cowboy:start_tls(3) or ranch:start_listener(3) function.
  Return value The atom ok is returned on success.
The {error, not_found} tuple is returned when the listener does not exist.</description>
    </item>
    
    <item>
      <title>cowboy:stop_listener(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy.stop_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy.stop_listener/</guid>
      <description>Name cowboy:stop_listener - Stop the given listener
Description stop_listener(Name :: ranch:ref()) -&amp;gt; ok | {error, not_found}.  Stop a previously started listener.
Alias of ranch:stop_listener(3).
Arguments Name The name of the listener to be stopped.
The name of the listener is the first argument given to the cowboy:start_clear(3), cowboy:start_tls(3) or ranch:start_listener(3) function.
  Return value The atom ok is returned on success.
The {error, not_found} tuple is returned when the listener does not exist.</description>
    </item>
    
    <item>
      <title>cowboy:stop_listener(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy.stop_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy.stop_listener/</guid>
      <description>Name cowboy:stop_listener - Stop the given listener
Description stop_listener(Name :: ranch:ref()) -&amp;gt; ok | {error, not_found}.  Stop a previously started listener.
Alias of ranch:stop_listener(3).
Arguments Name The name of the listener to be stopped.
The name of the listener is the first argument given to the cowboy:start_clear(3), cowboy:start_tls(3) or ranch:start_listener(3) function.
  Return value The atom ok is returned on success.
The {error, not_found} tuple is returned when the listener does not exist.</description>
    </item>
    
    <item>
      <title>cowboy:stop_listener(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy.stop_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy.stop_listener/</guid>
      <description>Name cowboy:stop_listener - Stop the given listener
Description stop_listener(Name :: ranch:ref()) -&amp;gt; ok | {error, not_found}.  Stop a previously started listener.
Alias of ranch:stop_listener(3).
Arguments Name The name of the listener to be stopped.
The name of the listener is the first argument given to the cowboy:start_clear(3), cowboy:start_tls(3) or ranch:start_listener(3) function.
  Return value The atom ok is returned on success.
The {error, not_found} tuple is returned when the listener does not exist.</description>
    </item>
    
    <item>
      <title>cowboy:stop_listener(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy.stop_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy.stop_listener/</guid>
      <description>Name cowboy:stop_listener - Stop the given listener
Description stop_listener(Name :: ranch:ref()) -&amp;gt; ok | {error, not_found}.  Stop a previously started listener.
Alias of ranch:stop_listener(3).
Arguments Name The name of the listener to be stopped.
The name of the listener is the first argument given to the cowboy:start_clear(3), cowboy:start_tls(3) or ranch:start_listener(3) function.
  Return value The atom ok is returned on success.
The {error, not_found} tuple is returned when the listener does not exist.</description>
    </item>
    
    <item>
      <title>cowboy_compress_h(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_compress_h/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_compress_h/</guid>
      <description>Name cowboy_compress_h - Compress stream handler
Description The module cowboy_compress_h compresses response bodies automatically when the client supports it. It will not try to compress responses that already have a content encoding.
Normal responses will only be compressed when their size is lower than the configured threshold. Streamed responses are always compressed, including when the sendfile command is used. Because the file must be read in memory to be compressed, this module is not suitable for automatically compressing large files.</description>
    </item>
    
    <item>
      <title>cowboy_compress_h(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_compress_h/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_compress_h/</guid>
      <description>Name cowboy_compress_h - Compress stream handler
Description The module cowboy_compress_h compresses response bodies automatically when the client supports it. It will not try to compress responses that already have a content encoding.
Normal responses will only be compressed when their size is lower than the configured threshold. Streamed responses are always compressed, including when the sendfile command is used. Because the file must be read in memory to be compressed, this module is not suitable for automatically compressing large files.</description>
    </item>
    
    <item>
      <title>cowboy_constraints(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_constraints/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_constraints/</guid>
      <description>Name cowboy_constraints - Constraints
Description The module cowboy_constraints defines the built-in constraints in Cowboy and provides an interface for manipulating these constraints.
Constraints are functions that define what type of input is allowed. They are used throughout Cowboy, from the router to query strings to cookies.
Exports Built-in constraints:
cowboy_constraints:int(3) - Integer constraint  cowboy_constraints:nonempty(3) - Non-empty constraint   Types constraint() constraint() :: int | nonempty | fun()  A constraint function.</description>
    </item>
    
    <item>
      <title>cowboy_constraints(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_constraints/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_constraints/</guid>
      <description>Name cowboy_constraints - Constraints
Description The module cowboy_constraints defines the built-in constraints in Cowboy and provides an interface for manipulating these constraints.
Constraints are functions that define what type of input is allowed. They are used throughout Cowboy, from the router to query strings to cookies.
Exports Built-in constraints:
cowboy_constraints:int(3) - Integer constraint  cowboy_constraints:nonempty(3) - Non-empty constraint   Types constraint() constraint() :: int | nonempty | fun()  A constraint function.</description>
    </item>
    
    <item>
      <title>cowboy_constraints(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_constraints/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_constraints/</guid>
      <description>Name cowboy_constraints - Constraints
Description The module cowboy_constraints defines the built-in constraints in Cowboy and provides an interface for manipulating these constraints.
Constraints are functions that define what type of input is allowed. They are used throughout Cowboy, from the router to query strings to cookies.
Exports Built-in constraints:
cowboy_constraints:int(3) - Integer constraint  cowboy_constraints:nonempty(3) - Non-empty constraint   Types constraint() constraint() :: int | nonempty | fun()  A constraint function.</description>
    </item>
    
    <item>
      <title>cowboy_constraints(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_constraints/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_constraints/</guid>
      <description>Name cowboy_constraints - Constraints
Description The module cowboy_constraints defines the built-in constraints in Cowboy and provides an interface for manipulating these constraints.
Constraints are functions that define what type of input is allowed. They are used throughout Cowboy, from the router to query strings to cookies.
Exports Built-in constraints:
cowboy_constraints:int(3) - Integer constraint  cowboy_constraints:nonempty(3) - Non-empty constraint   Types constraint() constraint() :: int | nonempty | fun()  A constraint function.</description>
    </item>
    
    <item>
      <title>cowboy_constraints(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_constraints/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_constraints/</guid>
      <description>Name cowboy_constraints - Constraints
Description The module cowboy_constraints defines the built-in constraints in Cowboy and provides an interface for manipulating these constraints.
Constraints are functions that define what type of input is allowed. They are used throughout Cowboy, from the router to query strings to cookies.
Exports Built-in constraints:
cowboy_constraints:int(3) - Integer constraint  cowboy_constraints:nonempty(3) - Non-empty constraint   Types constraint() constraint() :: int | nonempty | fun()  A constraint function.</description>
    </item>
    
    <item>
      <title>cowboy_constraints(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_constraints/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_constraints/</guid>
      <description>Name cowboy_constraints - Constraints
Description The module cowboy_constraints defines the built-in constraints in Cowboy and provides an interface for manipulating these constraints.
Constraints are functions that define what type of input is allowed. They are used throughout Cowboy, from the router to query strings to cookies.
Exports Built-in constraints:
cowboy_constraints:int(3) - Integer constraint  cowboy_constraints:nonempty(3) - Non-empty constraint   Types constraint() constraint() :: int | nonempty | fun()  A constraint function.</description>
    </item>
    
    <item>
      <title>cowboy_constraints:int(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_constraints.int/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_constraints.int/</guid>
      <description>Name cowboy_constraints:int - Integer constraint
Description Constraint functions implement a number of different operations.
int(forward, Bin) -&amp;gt; {ok, Int} | {error, not_an_integer} Bin :: binary() Int :: integer()  Validate and convert the text representation of an integer.
int(reverse, Int) -&amp;gt; {ok, Bin} | {error, not_an_integer}  Convert an integer back to its text representation.
int(format_error, Error) -&amp;gt; HumanReadable Error :: {not_an_integer, Bin | Int} HumanReadable :: iolist()  Generate a human-readable error message.</description>
    </item>
    
    <item>
      <title>cowboy_constraints:int(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_constraints.int/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_constraints.int/</guid>
      <description>Name cowboy_constraints:int - Integer constraint
Description Constraint functions implement a number of different operations.
int(forward, Bin) -&amp;gt; {ok, Int} | {error, not_an_integer} Bin :: binary() Int :: integer()  Validate and convert the text representation of an integer.
int(reverse, Int) -&amp;gt; {ok, Bin} | {error, not_an_integer}  Convert an integer back to its text representation.
int(format_error, Error) -&amp;gt; HumanReadable Error :: {not_an_integer, Bin | Int} HumanReadable :: iolist()  Generate a human-readable error message.</description>
    </item>
    
    <item>
      <title>cowboy_constraints:int(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_constraints.int/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_constraints.int/</guid>
      <description>Name cowboy_constraints:int - Integer constraint
Description Constraint functions implement a number of different operations.
int(forward, Bin) -&amp;gt; {ok, Int} | {error, not_an_integer} Bin :: binary() Int :: integer()  Validate and convert the text representation of an integer.
int(reverse, Int) -&amp;gt; {ok, Bin} | {error, not_an_integer}  Convert an integer back to its text representation.
int(format_error, Error) -&amp;gt; HumanReadable Error :: {not_an_integer, Bin | Int} HumanReadable :: iolist()  Generate a human-readable error message.</description>
    </item>
    
    <item>
      <title>cowboy_constraints:int(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_constraints.int/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_constraints.int/</guid>
      <description>Name cowboy_constraints:int - Integer constraint
Description Constraint functions implement a number of different operations.
int(forward, Bin) -&amp;gt; {ok, Int} | {error, not_an_integer} Bin :: binary() Int :: integer()  Validate and convert the text representation of an integer.
int(reverse, Int) -&amp;gt; {ok, Bin} | {error, not_an_integer}  Convert an integer back to its text representation.
int(format_error, Error) -&amp;gt; HumanReadable Error :: {not_an_integer, Bin | Int} HumanReadable :: iolist()  Generate a human-readable error message.</description>
    </item>
    
    <item>
      <title>cowboy_constraints:int(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_constraints.int/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_constraints.int/</guid>
      <description>Name cowboy_constraints:int - Integer constraint
Description Constraint functions implement a number of different operations.
int(forward, Bin) -&amp;gt; {ok, Int} | {error, not_an_integer} Bin :: binary() Int :: integer()  Validate and convert the text representation of an integer.
int(reverse, Int) -&amp;gt; {ok, Bin} | {error, not_an_integer}  Convert an integer back to its text representation.
int(format_error, Error) -&amp;gt; HumanReadable Error :: {not_an_integer, Bin | Int} HumanReadable :: iolist()  Generate a human-readable error message.</description>
    </item>
    
    <item>
      <title>cowboy_constraints:int(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_constraints.int/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_constraints.int/</guid>
      <description>Name cowboy_constraints:int - Integer constraint
Description Constraint functions implement a number of different operations.
int(forward, Bin) -&amp;gt; {ok, Int} | {error, not_an_integer} Bin :: binary() Int :: integer()  Validate and convert the text representation of an integer.
int(reverse, Int) -&amp;gt; {ok, Bin} | {error, not_an_integer}  Convert an integer back to its text representation.
int(format_error, Error) -&amp;gt; HumanReadable Error :: {not_an_integer, Bin | Int} HumanReadable :: iolist()  Generate a human-readable error message.</description>
    </item>
    
    <item>
      <title>cowboy_constraints:nonempty(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_constraints.nonempty/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_constraints.nonempty/</guid>
      <description>Name cowboy_constraints:nonempty - Non-empty constraint
Description Constraint functions implement a number of different operations.
nonempty(forward | reverse, &amp;lt;&amp;lt;&amp;gt;&amp;gt;) -&amp;gt; {error, empty}  Reject empty values.
nonempty(forward | reverse, Bin) -&amp;gt; {ok, Bin} Bin :: binary()  Accept any other binary values.
nonempty(format_error, Error) -&amp;gt; HumanReadable Error :: {empty, Bin} HumanReadable :: iolist()  Generate a human-readable error message.
Arguments Arguments vary depending on the operation. Constraint functions always take the operation type as first argument, and the value as second argument.</description>
    </item>
    
    <item>
      <title>cowboy_constraints:nonempty(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_constraints.nonempty/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_constraints.nonempty/</guid>
      <description>Name cowboy_constraints:nonempty - Non-empty constraint
Description Constraint functions implement a number of different operations.
nonempty(forward | reverse, &amp;lt;&amp;lt;&amp;gt;&amp;gt;) -&amp;gt; {error, empty}  Reject empty values.
nonempty(forward | reverse, Bin) -&amp;gt; {ok, Bin} Bin :: binary()  Accept any other binary values.
nonempty(format_error, Error) -&amp;gt; HumanReadable Error :: {empty, Bin} HumanReadable :: iolist()  Generate a human-readable error message.
Arguments Arguments vary depending on the operation. Constraint functions always take the operation type as first argument, and the value as second argument.</description>
    </item>
    
    <item>
      <title>cowboy_constraints:nonempty(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_constraints.nonempty/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_constraints.nonempty/</guid>
      <description>Name cowboy_constraints:nonempty - Non-empty constraint
Description Constraint functions implement a number of different operations.
nonempty(forward | reverse, &amp;lt;&amp;lt;&amp;gt;&amp;gt;) -&amp;gt; {error, empty}  Reject empty values.
nonempty(forward | reverse, Bin) -&amp;gt; {ok, Bin} Bin :: binary()  Accept any other binary values.
nonempty(format_error, Error) -&amp;gt; HumanReadable Error :: {empty, Bin} HumanReadable :: iolist()  Generate a human-readable error message.
Arguments Arguments vary depending on the operation. Constraint functions always take the operation type as first argument, and the value as second argument.</description>
    </item>
    
    <item>
      <title>cowboy_constraints:nonempty(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_constraints.nonempty/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_constraints.nonempty/</guid>
      <description>Name cowboy_constraints:nonempty - Non-empty constraint
Description Constraint functions implement a number of different operations.
nonempty(forward | reverse, &amp;lt;&amp;lt;&amp;gt;&amp;gt;) -&amp;gt; {error, empty}  Reject empty values.
nonempty(forward | reverse, Bin) -&amp;gt; {ok, Bin} Bin :: binary()  Accept any other binary values.
nonempty(format_error, Error) -&amp;gt; HumanReadable Error :: {empty, Bin} HumanReadable :: iolist()  Generate a human-readable error message.
Arguments Arguments vary depending on the operation. Constraint functions always take the operation type as first argument, and the value as second argument.</description>
    </item>
    
    <item>
      <title>cowboy_constraints:nonempty(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_constraints.nonempty/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_constraints.nonempty/</guid>
      <description>Name cowboy_constraints:nonempty - Non-empty constraint
Description Constraint functions implement a number of different operations.
nonempty(forward | reverse, &amp;lt;&amp;lt;&amp;gt;&amp;gt;) -&amp;gt; {error, empty}  Reject empty values.
nonempty(forward | reverse, Bin) -&amp;gt; {ok, Bin} Bin :: binary()  Accept any other binary values.
nonempty(format_error, Error) -&amp;gt; HumanReadable Error :: {empty, Bin} HumanReadable :: iolist()  Generate a human-readable error message.
Arguments Arguments vary depending on the operation. Constraint functions always take the operation type as first argument, and the value as second argument.</description>
    </item>
    
    <item>
      <title>cowboy_constraints:nonempty(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_constraints.nonempty/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_constraints.nonempty/</guid>
      <description>Name cowboy_constraints:nonempty - Non-empty constraint
Description Constraint functions implement a number of different operations.
nonempty(forward | reverse, &amp;lt;&amp;lt;&amp;gt;&amp;gt;) -&amp;gt; {error, empty}  Reject empty values.
nonempty(forward | reverse, Bin) -&amp;gt; {ok, Bin} Bin :: binary()  Accept any other binary values.
nonempty(format_error, Error) -&amp;gt; HumanReadable Error :: {empty, Bin} HumanReadable :: iolist()  Generate a human-readable error message.
Arguments Arguments vary depending on the operation. Constraint functions always take the operation type as first argument, and the value as second argument.</description>
    </item>
    
    <item>
      <title>cowboy_handler(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_handler/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_handler/</guid>
      <description>Name cowboy_handler - Plain HTTP handlers
Description The cowboy_handler middleware executes the handler selected by the router or any other preceding middleware.
This middleware takes the handler module and initial state from the handler and handler_opts environment values, respectively. On completion, it adds a result value to the middleware environment, containing the return value of the terminate/3 callback (if defined) and ok otherwise.
This module also defines a callback interface for handling HTTP requests.</description>
    </item>
    
    <item>
      <title>cowboy_handler(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_handler/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_handler/</guid>
      <description>Name cowboy_handler - Plain HTTP handlers
Description The cowboy_handler middleware executes the handler selected by the router or any other preceding middleware.
This middleware takes the handler module and initial state from the handler and handler_opts environment values, respectively. On completion, it adds a result value to the middleware environment, containing the return value of the terminate/3 callback (if defined) and ok otherwise.
This module also defines a callback interface for handling HTTP requests.</description>
    </item>
    
    <item>
      <title>cowboy_handler(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_handler/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_handler/</guid>
      <description>Name cowboy_handler - Plain HTTP handlers
Description The cowboy_handler middleware executes the handler selected by the router or any other preceding middleware.
This middleware takes the handler module and initial state from the handler and handler_opts environment values, respectively. On completion, it adds a result value to the middleware environment, containing the return value of the terminate/3 callback (if defined) and ok otherwise.
This module also defines a callback interface for handling HTTP requests.</description>
    </item>
    
    <item>
      <title>cowboy_handler(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_handler/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_handler/</guid>
      <description>Name cowboy_handler - Plain HTTP handlers
Description The cowboy_handler middleware executes the handler selected by the router or any other preceding middleware.
This middleware takes the handler module and initial state from the handler and handler_opts environment values, respectively. On completion, it adds a result value to the middleware environment, containing the return value of the terminate/3 callback (if defined) and ok otherwise.
This module also defines a callback interface for handling HTTP requests.</description>
    </item>
    
    <item>
      <title>cowboy_handler(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_handler/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_handler/</guid>
      <description>Name cowboy_handler - Plain HTTP handlers
Description The cowboy_handler middleware executes the handler selected by the router or any other preceding middleware.
This middleware takes the handler module and initial state from the handler and handler_opts environment values, respectively. On completion, it adds a result value to the middleware environment, containing the return value of the terminate/3 callback (if defined) and ok otherwise.
This module also defines a callback interface for handling HTTP requests.</description>
    </item>
    
    <item>
      <title>cowboy_handler(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_handler/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_handler/</guid>
      <description>Name cowboy_handler - Plain HTTP handlers
Description The cowboy_handler middleware executes the handler selected by the router or any other preceding middleware.
This middleware takes the handler module and initial state from the handler and handler_opts environment values, respectively. On completion, it adds a result value to the middleware environment, containing the return value of the terminate/3 callback (if defined) and ok otherwise.
This module also defines a callback interface for handling HTTP requests.</description>
    </item>
    
    <item>
      <title>cowboy_handler:terminate(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_handler.terminate/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_handler.terminate/</guid>
      <description>Name cowboy_handler:terminate - Terminate the handler
Description terminate(Reason, PartialReq, State, Handler) -&amp;gt; ok Reason :: any() PartialReq :: map() State :: any() Handler :: module()  Call the optional terminate callback if it is defined.
Make sure to use this function at the end of the execution of modules that implement custom handler behaviors.
Arguments Reason Reason for termination.
 PartialReq The Req object.
It is possible to remove fields from the Req object to save memory when the handler has no concept of requests/responses.</description>
    </item>
    
    <item>
      <title>cowboy_handler:terminate(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_handler.terminate/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_handler.terminate/</guid>
      <description>Name cowboy_handler:terminate - Terminate the handler
Description terminate(Reason, PartialReq, State, Handler) -&amp;gt; ok Reason :: any() PartialReq :: map() State :: any() Handler :: module()  Call the optional terminate callback if it is defined.
Make sure to use this function at the end of the execution of modules that implement custom handler behaviors.
Arguments Reason Reason for termination.
 PartialReq The Req object.
It is possible to remove fields from the Req object to save memory when the handler has no concept of requests/responses.</description>
    </item>
    
    <item>
      <title>cowboy_handler:terminate(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_handler.terminate/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_handler.terminate/</guid>
      <description>Name cowboy_handler:terminate - Terminate the handler
Description terminate(Reason, PartialReq, State, Handler) -&amp;gt; ok Reason :: any() PartialReq :: map() State :: any() Handler :: module()  Call the optional terminate callback if it is defined.
Make sure to use this function at the end of the execution of modules that implement custom handler behaviors.
Arguments Reason Reason for termination.
 PartialReq The Req object.
It is possible to remove fields from the Req object to save memory when the handler has no concept of requests/responses.</description>
    </item>
    
    <item>
      <title>cowboy_handler:terminate(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_handler.terminate/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_handler.terminate/</guid>
      <description>Name cowboy_handler:terminate - Terminate the handler
Description terminate(Reason, PartialReq, State, Handler) -&amp;gt; ok Reason :: any() PartialReq :: map() State :: any() Handler :: module()  Call the optional terminate callback if it is defined.
Make sure to use this function at the end of the execution of modules that implement custom handler behaviors.
Arguments Reason Reason for termination.
 PartialReq The Req object.
It is possible to remove fields from the Req object to save memory when the handler has no concept of requests/responses.</description>
    </item>
    
    <item>
      <title>cowboy_handler:terminate(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_handler.terminate/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_handler.terminate/</guid>
      <description>Name cowboy_handler:terminate - Terminate the handler
Description terminate(Reason, PartialReq, State, Handler) -&amp;gt; ok Reason :: any() PartialReq :: map() State :: any() Handler :: module()  Call the optional terminate callback if it is defined.
Make sure to use this function at the end of the execution of modules that implement custom handler behaviors.
Arguments Reason Reason for termination.
 PartialReq The Req object.
It is possible to remove fields from the Req object to save memory when the handler has no concept of requests/responses.</description>
    </item>
    
    <item>
      <title>cowboy_handler:terminate(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_handler.terminate/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_handler.terminate/</guid>
      <description>Name cowboy_handler:terminate - Terminate the handler
Description terminate(Reason, PartialReq, State, Handler) -&amp;gt; ok Reason :: any() PartialReq :: map() State :: any() Handler :: module()  Call the optional terminate callback if it is defined.
Make sure to use this function at the end of the execution of modules that implement custom handler behaviors.
Arguments Reason Reason for termination.
 PartialReq The Req object.
It is possible to remove fields from the Req object to save memory when the handler has no concept of requests/responses.</description>
    </item>
    
    <item>
      <title>cowboy_http(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_http/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_http/</guid>
      <description>Name cowboy_http - HTTP/1.1
Description The module cowboy_http implements HTTP/1.1 and HTTP/1.0 as a Ranch protocol.
Options opts() :: #{ connection_type =&amp;gt; worker | supervisor, env =&amp;gt; cowboy_middleware:env(), idle_timeout =&amp;gt; timeout(), inactivity_timeout =&amp;gt; timeout(), max_empty_lines =&amp;gt; non_neg_integer(), max_header_name_length =&amp;gt; non_neg_integer(), max_header_value_length =&amp;gt; non_neg_integer(), max_headers =&amp;gt; non_neg_integer(), max_keepalive =&amp;gt; non_neg_integer(), max_method_length =&amp;gt; non_neg_integer(), max_request_line_length =&amp;gt; non_neg_integer(), max_skip_body_length =&amp;gt; non_neg_integer(), middlewares =&amp;gt; [module()], request_timeout =&amp;gt; timeout(), shutdown_timeout =&amp;gt; timeout(), stream_handlers =&amp;gt; [module()] }  Configuration for the HTTP/1.</description>
    </item>
    
    <item>
      <title>cowboy_http(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_http/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_http/</guid>
      <description>Name cowboy_http - HTTP/1.1
Description The module cowboy_http implements HTTP/1.1 and HTTP/1.0 as a Ranch protocol.
Options opts() :: #{ connection_type =&amp;gt; worker | supervisor, env =&amp;gt; cowboy_middleware:env(), idle_timeout =&amp;gt; timeout(), inactivity_timeout =&amp;gt; timeout(), max_empty_lines =&amp;gt; non_neg_integer(), max_header_name_length =&amp;gt; non_neg_integer(), max_header_value_length =&amp;gt; non_neg_integer(), max_headers =&amp;gt; non_neg_integer(), max_keepalive =&amp;gt; non_neg_integer(), max_method_length =&amp;gt; non_neg_integer(), max_request_line_length =&amp;gt; non_neg_integer(), max_skip_body_length =&amp;gt; non_neg_integer(), middlewares =&amp;gt; [module()], request_timeout =&amp;gt; timeout(), shutdown_timeout =&amp;gt; timeout(), stream_handlers =&amp;gt; [module()] }  Configuration for the HTTP/1.</description>
    </item>
    
    <item>
      <title>cowboy_http(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_http/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_http/</guid>
      <description>Name cowboy_http - HTTP/1.1
Description The module cowboy_http implements HTTP/1.1 and HTTP/1.0 as a Ranch protocol.
Options opts() :: #{ connection_type =&amp;gt; worker | supervisor, env =&amp;gt; cowboy_middleware:env(), idle_timeout =&amp;gt; timeout(), inactivity_timeout =&amp;gt; timeout(), max_empty_lines =&amp;gt; non_neg_integer(), max_header_name_length =&amp;gt; non_neg_integer(), max_header_value_length =&amp;gt; non_neg_integer(), max_headers =&amp;gt; non_neg_integer(), max_keepalive =&amp;gt; non_neg_integer(), max_method_length =&amp;gt; non_neg_integer(), max_request_line_length =&amp;gt; non_neg_integer(), max_skip_body_length =&amp;gt; non_neg_integer(), middlewares =&amp;gt; [module()], request_timeout =&amp;gt; timeout(), shutdown_timeout =&amp;gt; timeout(), stream_handlers =&amp;gt; [module()] }  Configuration for the HTTP/1.</description>
    </item>
    
    <item>
      <title>cowboy_http(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_http/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_http/</guid>
      <description>Name cowboy_http - HTTP/1.1
Description The module cowboy_http implements HTTP/1.1 and HTTP/1.0 as a Ranch protocol.
Options opts() :: #{ connection_type =&amp;gt; worker | supervisor, env =&amp;gt; cowboy_middleware:env(), idle_timeout =&amp;gt; timeout(), inactivity_timeout =&amp;gt; timeout(), linger_timeout =&amp;gt; timeout(), max_empty_lines =&amp;gt; non_neg_integer(), max_header_name_length =&amp;gt; non_neg_integer(), max_header_value_length =&amp;gt; non_neg_integer(), max_headers =&amp;gt; non_neg_integer(), max_keepalive =&amp;gt; non_neg_integer(), max_method_length =&amp;gt; non_neg_integer(), max_request_line_length =&amp;gt; non_neg_integer(), max_skip_body_length =&amp;gt; non_neg_integer(), middlewares =&amp;gt; [module()], request_timeout =&amp;gt; timeout(), shutdown_timeout =&amp;gt; timeout(), stream_handlers =&amp;gt; [module()] }  Configuration for the HTTP/1.</description>
    </item>
    
    <item>
      <title>cowboy_http(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_http/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_http/</guid>
      <description>Name cowboy_http - HTTP/1.1
Description The module cowboy_http implements HTTP/1.1 and HTTP/1.0 as a Ranch protocol.
Options opts() :: #{ chunked =&amp;gt; boolean(), connection_type =&amp;gt; worker | supervisor, http10_keepalive =&amp;gt; boolean(), idle_timeout =&amp;gt; timeout(), inactivity_timeout =&amp;gt; timeout(), linger_timeout =&amp;gt; timeout(), max_empty_lines =&amp;gt; non_neg_integer(), max_header_name_length =&amp;gt; non_neg_integer(), max_header_value_length =&amp;gt; non_neg_integer(), max_headers =&amp;gt; non_neg_integer(), max_keepalive =&amp;gt; non_neg_integer(), max_method_length =&amp;gt; non_neg_integer(), max_request_line_length =&amp;gt; non_neg_integer(), max_skip_body_length =&amp;gt; non_neg_integer(), proxy_header =&amp;gt; boolean(), request_timeout =&amp;gt; timeout(), sendfile =&amp;gt; boolean(), stream_handlers =&amp;gt; [module()] }  Configuration for the HTTP/1.</description>
    </item>
    
    <item>
      <title>cowboy_http(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_http/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_http/</guid>
      <description>Name cowboy_http - HTTP/1.1
Description The module cowboy_http implements HTTP/1.1 and HTTP/1.0 as a Ranch protocol.
Options opts() :: #{ chunked =&amp;gt; boolean(), connection_type =&amp;gt; worker | supervisor, http10_keepalive =&amp;gt; boolean(), idle_timeout =&amp;gt; timeout(), inactivity_timeout =&amp;gt; timeout(), initial_stream_flow_size =&amp;gt; non_neg_integer(), linger_timeout =&amp;gt; timeout(), logger =&amp;gt; module(), max_empty_lines =&amp;gt; non_neg_integer(), max_header_name_length =&amp;gt; non_neg_integer(), max_header_value_length =&amp;gt; non_neg_integer(), max_headers =&amp;gt; non_neg_integer(), max_keepalive =&amp;gt; non_neg_integer(), max_method_length =&amp;gt; non_neg_integer(), max_request_line_length =&amp;gt; non_neg_integer(), max_skip_body_length =&amp;gt; non_neg_integer(), proxy_header =&amp;gt; boolean(), request_timeout =&amp;gt; timeout(), sendfile =&amp;gt; boolean(), stream_handlers =&amp;gt; [module()] }  Configuration for the HTTP/1.</description>
    </item>
    
    <item>
      <title>cowboy_http2(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_http2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_http2/</guid>
      <description>Name cowboy_http2 - HTTP/2
Description The module cowboy_http2 implements HTTP/2 as a Ranch protocol.
Options opts() :: #{ connection_type =&amp;gt; worker | supervisor, env =&amp;gt; cowboy_middleware:env(), inactivity_timeout =&amp;gt; timeout(), middlewares =&amp;gt; [module()], preface_timeout =&amp;gt; timeout(), shutdown_timeout =&amp;gt; timeout(), stream_handlers =&amp;gt; [module()] }  Configuration for the HTTP/2 protocol.
This configuration is passed to Cowboy when starting listeners using cowboy:start_clear/3 or cowboy:start_tls/3 functions.
It can be updated without restarting listeners using the Ranch functions ranch:get_protocol_options/1 and ranch:set_protocol_options/2.</description>
    </item>
    
    <item>
      <title>cowboy_http2(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_http2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_http2/</guid>
      <description>Name cowboy_http2 - HTTP/2
Description The module cowboy_http2 implements HTTP/2 as a Ranch protocol.
Options opts() :: #{ connection_type =&amp;gt; worker | supervisor, env =&amp;gt; cowboy_middleware:env(), inactivity_timeout =&amp;gt; timeout(), middlewares =&amp;gt; [module()], preface_timeout =&amp;gt; timeout(), shutdown_timeout =&amp;gt; timeout(), stream_handlers =&amp;gt; [module()] }  Configuration for the HTTP/2 protocol.
This configuration is passed to Cowboy when starting listeners using cowboy:start_clear/3 or cowboy:start_tls/3 functions.
It can be updated without restarting listeners using the Ranch functions ranch:get_protocol_options/1 and ranch:set_protocol_options/2.</description>
    </item>
    
    <item>
      <title>cowboy_http2(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_http2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_http2/</guid>
      <description>Name cowboy_http2 - HTTP/2
Description The module cowboy_http2 implements HTTP/2 as a Ranch protocol.
Options opts() :: #{ connection_type =&amp;gt; worker | supervisor, enable_connect_protocol =&amp;gt; boolean(), env =&amp;gt; cowboy_middleware:env(), inactivity_timeout =&amp;gt; timeout(), initial_connection_window_size =&amp;gt; 65535..16#7fffffff, initial_stream_window_size =&amp;gt; 0..16#7fffffff, max_concurrent_streams =&amp;gt; non_neg_integer() | infinity, max_decode_table_size =&amp;gt; non_neg_integer(), max_encode_table_size =&amp;gt; non_neg_integer(), max_frame_size_received =&amp;gt; 16384..16777215, max_frame_size_sent =&amp;gt; 16384..16777215 | infinity, middlewares =&amp;gt; [module()], preface_timeout =&amp;gt; timeout(), settings_timeout =&amp;gt; timeout(), shutdown_timeout =&amp;gt; timeout(), stream_handlers =&amp;gt; [module()] }  Configuration for the HTTP/2 protocol.</description>
    </item>
    
    <item>
      <title>cowboy_http2(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_http2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_http2/</guid>
      <description>Name cowboy_http2 - HTTP/2
Description The module cowboy_http2 implements HTTP/2 as a Ranch protocol.
Options opts() :: #{ connection_type =&amp;gt; worker | supervisor, enable_connect_protocol =&amp;gt; boolean(), env =&amp;gt; cowboy_middleware:env(), inactivity_timeout =&amp;gt; timeout(), initial_connection_window_size =&amp;gt; 65535..16#7fffffff, initial_stream_window_size =&amp;gt; 0..16#7fffffff, max_concurrent_streams =&amp;gt; non_neg_integer() | infinity, max_decode_table_size =&amp;gt; non_neg_integer(), max_encode_table_size =&amp;gt; non_neg_integer(), max_frame_size_received =&amp;gt; 16384..16777215, max_frame_size_sent =&amp;gt; 16384..16777215 | infinity, middlewares =&amp;gt; [module()], preface_timeout =&amp;gt; timeout(), settings_timeout =&amp;gt; timeout(), shutdown_timeout =&amp;gt; timeout(), stream_handlers =&amp;gt; [module()] }  Configuration for the HTTP/2 protocol.</description>
    </item>
    
    <item>
      <title>cowboy_http2(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_http2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_http2/</guid>
      <description>Name cowboy_http2 - HTTP/2
Description The module cowboy_http2 implements HTTP/2 as a Ranch protocol.
Options opts() :: #{ connection_type =&amp;gt; worker | supervisor, enable_connect_protocol =&amp;gt; boolean(), idle_timeout =&amp;gt; timeout(), inactivity_timeout =&amp;gt; timeout(), initial_connection_window_size =&amp;gt; 65535..16#7fffffff, initial_stream_window_size =&amp;gt; 0..16#7fffffff, max_concurrent_streams =&amp;gt; non_neg_integer() | infinity, max_decode_table_size =&amp;gt; non_neg_integer(), max_encode_table_size =&amp;gt; non_neg_integer(), max_frame_size_received =&amp;gt; 16384..16777215, max_frame_size_sent =&amp;gt; 16384..16777215 | infinity, preface_timeout =&amp;gt; timeout(), proxy_header =&amp;gt; boolean(), sendfile =&amp;gt; boolean(), settings_timeout =&amp;gt; timeout(), stream_handlers =&amp;gt; [module()] }  Configuration for the HTTP/2 protocol.</description>
    </item>
    
    <item>
      <title>cowboy_http2(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_http2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_http2/</guid>
      <description>Name cowboy_http2 - HTTP/2
Description The module cowboy_http2 implements HTTP/2 as a Ranch protocol.
Options opts() :: #{ connection_type =&amp;gt; worker | supervisor, connection_window_margin_size =&amp;gt; 0..16#7fffffff, connection_window_update_threshold =&amp;gt; 0..16#7fffffff, enable_connect_protocol =&amp;gt; boolean(), idle_timeout =&amp;gt; timeout(), inactivity_timeout =&amp;gt; timeout(), initial_connection_window_size =&amp;gt; 65535..16#7fffffff, initial_stream_window_size =&amp;gt; 0..16#7fffffff, logger =&amp;gt; module(), max_concurrent_streams =&amp;gt; non_neg_integer() | infinity, max_connection_buffer_size =&amp;gt; non_neg_integer(), max_connection_window_size =&amp;gt; 0..16#7fffffff, max_decode_table_size =&amp;gt; non_neg_integer(), max_encode_table_size =&amp;gt; non_neg_integer(), max_frame_size_received =&amp;gt; 16384..16777215, max_frame_size_sent =&amp;gt; 16384..16777215 | infinity, max_received_frame_rate =&amp;gt; {pos_integer(), timeout()}, max_reset_stream_rate =&amp;gt; {pos_integer(), timeout()}, max_stream_buffer_size =&amp;gt; non_neg_integer(), max_stream_window_size =&amp;gt; 0.</description>
    </item>
    
    <item>
      <title>cowboy_loop(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_loop/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_loop/</guid>
      <description>Name cowboy_loop - Loop handlers
Description The module cowboy_loop defines a callback interface for long running HTTP connections.
You should switch to this behavior for long polling, server-sent events and similar long-running requests.
There are generally two usage patterns:
Loop until receiving a specific message, then send a response and stop execution (for example long polling);  Or initiate a response in init/2 and stream the body in info/3 as necessary (for example server-sent events).</description>
    </item>
    
    <item>
      <title>cowboy_loop(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_loop/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_loop/</guid>
      <description>Name cowboy_loop - Loop handlers
Description The module cowboy_loop defines a callback interface for long running HTTP connections.
You should switch to this behavior for long polling, server-sent events and similar long-running requests.
There are generally two usage patterns:
Loop until receiving a specific message, then send a response and stop execution (for example long polling);  Or initiate a response in init/2 and stream the body in info/3 as necessary (for example server-sent events).</description>
    </item>
    
    <item>
      <title>cowboy_loop(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_loop/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_loop/</guid>
      <description>Name cowboy_loop - Loop handlers
Description The module cowboy_loop defines a callback interface for long running HTTP connections.
You should switch to this behavior for long polling, server-sent events and similar long-running requests.
There are generally two usage patterns:
Loop until receiving a specific message, then send a response and stop execution (for example long polling);  Or initiate a response in init/2 and stream the body in info/3 as necessary (for example server-sent events).</description>
    </item>
    
    <item>
      <title>cowboy_loop(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_loop/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_loop/</guid>
      <description>Name cowboy_loop - Loop handlers
Description The module cowboy_loop defines a callback interface for long running HTTP connections.
You should switch to this behavior for long polling, server-sent events and similar long-running requests.
There are generally two usage patterns:
Loop until receiving a specific message, then send a response and stop execution (for example long polling);  Or initiate a response in init/2 and stream the body in info/3 as necessary (for example server-sent events).</description>
    </item>
    
    <item>
      <title>cowboy_loop(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_loop/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_loop/</guid>
      <description>Name cowboy_loop - Loop handlers
Description The module cowboy_loop defines a callback interface for long running HTTP connections.
You should switch to this behavior for long polling, server-sent events and similar long-running requests.
There are generally two usage patterns:
Loop until receiving a specific message, then send a response and stop execution (for example long polling);  Or initiate a response in init/2 and stream the body in info/3 as necessary (for example server-sent events).</description>
    </item>
    
    <item>
      <title>cowboy_loop(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_loop/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_loop/</guid>
      <description>Name cowboy_loop - Loop handlers
Description The module cowboy_loop defines a callback interface for long running HTTP connections.
You should switch to this behavior for long polling, server-sent events and similar long-running requests.
There are generally two usage patterns:
Loop until receiving a specific message, then send a response and stop execution (for example long polling);  Or initiate a response in init/2 and stream the body in info/3 as necessary (for example server-sent events).</description>
    </item>
    
    <item>
      <title>cowboy_metrics_h(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_metrics_h/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_metrics_h/</guid>
      <description>Name cowboy_metrics_h - Metrics stream handler
Description The module cowboy_metrics_h gathers metrics and other information about a stream. It then calls the configured callback with this data.
Types metrics() metrics() :: #{ %% The identifier for this listener. ref := ranch:ref(), %% The pid for this connection. pid := pid(), %% The streamid also indicates the total number of requests on %% this connection (StreamID div 2 + 1). streamid := cowboy_stream:streamid(), %% The terminate reason is always useful.</description>
    </item>
    
    <item>
      <title>cowboy_middleware(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_middleware/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_middleware/</guid>
      <description>Name cowboy_middleware - Middlewares
Description The module cowboy_middleware defines a callback interface for Cowboy middlewares.
Middlewares process the request sequentially in the order they are configured.
Callbacks Middlewares implement the following interface:
execute(Req, Env) -&amp;gt; {ok, Req, Env} | {suspend, module(), atom(), [any()]} | {stop, Req} Req :: cowboy_req:req() Env :: cowboy_middleware:env()  The execute/2 is the only callback that needs to be implemented. It must execute the middleware and return with instructions for Cowboy.</description>
    </item>
    
    <item>
      <title>cowboy_middleware(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_middleware/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_middleware/</guid>
      <description>Name cowboy_middleware - Middlewares
Description The module cowboy_middleware defines a callback interface for Cowboy middlewares.
Middlewares process the request sequentially in the order they are configured.
Callbacks Middlewares implement the following interface:
execute(Req, Env) -&amp;gt; {ok, Req, Env} | {suspend, module(), atom(), [any()]} | {stop, Req} Req :: cowboy_req:req() Env :: cowboy_middleware:env()  The execute/2 is the only callback that needs to be implemented. It must execute the middleware and return with instructions for Cowboy.</description>
    </item>
    
    <item>
      <title>cowboy_middleware(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_middleware/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_middleware/</guid>
      <description>Name cowboy_middleware - Middlewares
Description The module cowboy_middleware defines a callback interface for Cowboy middlewares.
Middlewares process the request sequentially in the order they are configured.
Callbacks Middlewares implement the following interface:
execute(Req, Env) -&amp;gt; {ok, Req, Env} | {suspend, module(), atom(), [any()]} | {stop, Req} Req :: cowboy_req:req() Env :: cowboy_middleware:env()  The execute/2 is the only callback that needs to be implemented. It must execute the middleware and return with instructions for Cowboy.</description>
    </item>
    
    <item>
      <title>cowboy_middleware(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_middleware/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_middleware/</guid>
      <description>Name cowboy_middleware - Middlewares
Description The module cowboy_middleware defines a callback interface for Cowboy middlewares.
Middlewares process the request sequentially in the order they are configured.
Callbacks Middlewares implement the following interface:
execute(Req, Env) -&amp;gt; {ok, Req, Env} | {suspend, module(), atom(), [any()]} | {stop, Req} Req :: cowboy_req:req() Env :: cowboy_middleware:env()  The execute/2 is the only callback that needs to be implemented. It must execute the middleware and return with instructions for Cowboy.</description>
    </item>
    
    <item>
      <title>cowboy_middleware(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_middleware/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_middleware/</guid>
      <description>Name cowboy_middleware - Middlewares
Description The module cowboy_middleware defines a callback interface for Cowboy middlewares.
Middlewares process the request sequentially in the order they are configured.
Callbacks Middlewares implement the following interface:
execute(Req, Env) -&amp;gt; {ok, Req, Env} | {suspend, module(), atom(), [any()]} | {stop, Req} Req :: cowboy_req:req() Env :: cowboy_middleware:env()  The execute/2 is the only callback that needs to be implemented. It must execute the middleware and return with instructions for Cowboy.</description>
    </item>
    
    <item>
      <title>cowboy_middleware(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_middleware/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_middleware/</guid>
      <description>Name cowboy_middleware - Middlewares
Description The module cowboy_middleware defines a callback interface for Cowboy middlewares.
Middlewares process the request sequentially in the order they are configured.
Callbacks Middlewares implement the following interface:
execute(Req, Env) -&amp;gt; {ok, Req, Env} | {suspend, module(), atom(), [any()]} | {stop, Req} Req :: cowboy_req:req() Env :: cowboy_middleware:env()  The execute/2 is the only callback that needs to be implemented. It must execute the middleware and return with instructions for Cowboy.</description>
    </item>
    
    <item>
      <title>cowboy_req(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req/</guid>
      <description>Name cowboy_req - HTTP request and response
Description The module cowboy_req provides functions to access, manipulate and respond to requests.
There are four types of functions in this module. They can be differentiated by their name and their return type:
Type Name pattern Return type access no verb, parse_*, match_* Value  question has_* boolean()  modification set_* Req  action any other verb ok | {Result, Value, Req}   Any Req returned must be used in place of the one passed as argument.</description>
    </item>
    
    <item>
      <title>cowboy_req(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req/</guid>
      <description>Name cowboy_req - HTTP request and response
Description The module cowboy_req provides functions to access, manipulate and respond to requests.
There are four types of functions in this module. They can be differentiated by their name and their return type:
Type Name pattern Return type access no verb, parse_*, match_* Value  question has_* boolean()  modification set_* Req  action any other verb ok | {Result, Value, Req}   Any Req returned must be used in place of the one passed as argument.</description>
    </item>
    
    <item>
      <title>cowboy_req(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req/</guid>
      <description>Name cowboy_req - HTTP request and response
Description The module cowboy_req provides functions to access, manipulate and respond to requests.
There are four types of functions in this module. They can be differentiated by their name and their return type:
Type Name pattern Return type access no verb, parse_*, match_* Value  question has_* boolean()  modification set_* Req  action any other verb ok | {Result, Value, Req}   Any Req returned must be used in place of the one passed as argument.</description>
    </item>
    
    <item>
      <title>cowboy_req(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req/</guid>
      <description>Name cowboy_req - HTTP request and response
Description The module cowboy_req provides functions to access, manipulate and respond to requests.
There are four types of functions in this module. They can be differentiated by their name and their return type:
Type Name pattern Return type access no verb, parse_*, match_* Value  question has_* boolean()  modification set_* Req  action any other verb ok | {Result, Value, Req}   Any Req returned must be used in place of the one passed as argument.</description>
    </item>
    
    <item>
      <title>cowboy_req(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req/</guid>
      <description>Name cowboy_req - HTTP request and response
Description The module cowboy_req provides functions to access, manipulate and respond to requests.
There are four types of functions in this module. They can be differentiated by their name and their return type:
Type Name pattern Return type access no verb, parse_*, match_* Value  question has_* boolean()  modification set_* Req  action any other verb ok | {Result, Value, Req}   Any Req returned must be used in place of the one passed as argument.</description>
    </item>
    
    <item>
      <title>cowboy_req(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req/</guid>
      <description>Name cowboy_req - HTTP request and response
Description The module cowboy_req provides functions to access, manipulate and respond to requests.
There are four types of functions in this module. They can be differentiated by their name and their return type:
Type Name pattern Return type access no verb, parse_*, match_* Value  question has_* boolean()  modification set_* Req  action any other verb ok | {Result, Value, Req}   Any Req returned must be used in place of the one passed as argument.</description>
    </item>
    
    <item>
      <title>cowboy_req:binding(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.binding/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.binding/</guid>
      <description>Name cowboy_req:binding - Access a value bound from the route
Description binding(Name, Req) -&amp;gt; binding(Name, Req, undefined) binding(Name, Req, Default) -&amp;gt; any() | Default Name :: atom() Req :: cowboy_req:req() Default :: any()  Return the value for the given binding.
Arguments Name Desired binding name as an atom.
 Req The Req object.
 Default Default value returned when the binding is missing.
  Return value By default the value is a case sensitive binary string, however constraints may change the type of this value (for example automatically converting numbers to integer).</description>
    </item>
    
    <item>
      <title>cowboy_req:binding(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.binding/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.binding/</guid>
      <description>Name cowboy_req:binding - Access a value bound from the route
Description binding(Name, Req) -&amp;gt; binding(Name, Req, undefined) binding(Name, Req, Default) -&amp;gt; any() | Default Name :: atom() Req :: cowboy_req:req() Default :: any()  Return the value for the given binding.
Arguments Name Desired binding name as an atom.
 Req The Req object.
 Default Default value returned when the binding is missing.
  Return value By default the value is a case sensitive binary string, however constraints may change the type of this value (for example automatically converting numbers to integer).</description>
    </item>
    
    <item>
      <title>cowboy_req:binding(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.binding/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.binding/</guid>
      <description>Name cowboy_req:binding - Access a value bound from the route
Description binding(Name, Req) -&amp;gt; binding(Name, Req, undefined) binding(Name, Req, Default) -&amp;gt; any() | Default Name :: atom() Req :: cowboy_req:req() Default :: any()  Return the value for the given binding.
Arguments Name Desired binding name as an atom.
 Req The Req object.
 Default Default value returned when the binding is missing.
  Return value By default the value is a case sensitive binary string, however constraints may change the type of this value (for example automatically converting numbers to integer).</description>
    </item>
    
    <item>
      <title>cowboy_req:binding(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.binding/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.binding/</guid>
      <description>Name cowboy_req:binding - Access a value bound from the route
Description binding(Name, Req) -&amp;gt; binding(Name, Req, undefined) binding(Name, Req, Default) -&amp;gt; any() | Default Name :: atom() Req :: cowboy_req:req() Default :: any()  Return the value for the given binding.
Arguments Name Desired binding name as an atom.
 Req The Req object.
 Default Default value returned when the binding is missing.
  Return value By default the value is a case sensitive binary string, however constraints may change the type of this value (for example automatically converting numbers to integer).</description>
    </item>
    
    <item>
      <title>cowboy_req:binding(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.binding/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.binding/</guid>
      <description>Name cowboy_req:binding - Access a value bound from the route
Description binding(Name, Req) -&amp;gt; binding(Name, Req, undefined) binding(Name, Req, Default) -&amp;gt; any() | Default Name :: atom() Req :: cowboy_req:req() Default :: any()  Return the value for the given binding.
Arguments Name Desired binding name as an atom.
 Req The Req object.
 Default Default value returned when the binding is missing.
  Return value By default the value is a case sensitive binary string, however constraints may change the type of this value (for example automatically converting numbers to integer).</description>
    </item>
    
    <item>
      <title>cowboy_req:binding(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.binding/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.binding/</guid>
      <description>Name cowboy_req:binding - Access a value bound from the route
Description binding(Name, Req) -&amp;gt; binding(Name, Req, undefined) binding(Name, Req, Default) -&amp;gt; any() | Default Name :: atom() Req :: cowboy_req:req() Default :: any()  Return the value for the given binding.
Arguments Name Desired binding name as an atom.
 Req The Req object.
 Default Default value returned when the binding is missing.
  Return value By default the value is a case sensitive binary string, however constraints may change the type of this value (for example automatically converting numbers to integer).</description>
    </item>
    
    <item>
      <title>cowboy_req:bindings(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.bindings/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.bindings/</guid>
      <description>Name cowboy_req:bindings - Access all values bound from the route
Description bindings(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:bindings()  Return a map containing all bindings.
Arguments Req The Req object.
  Return value By default values are case sensitive binary strings, however constraints may change the type of this value (for example automatically converting numbers to integer).
Changelog 2.0: Only the values are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:bindings(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.bindings/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.bindings/</guid>
      <description>Name cowboy_req:bindings - Access all values bound from the route
Description bindings(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:bindings()  Return a map containing all bindings.
Arguments Req The Req object.
  Return value By default values are case sensitive binary strings, however constraints may change the type of this value (for example automatically converting numbers to integer).
Changelog 2.0: Only the values are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:bindings(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.bindings/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.bindings/</guid>
      <description>Name cowboy_req:bindings - Access all values bound from the route
Description bindings(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:bindings()  Return a map containing all bindings.
Arguments Req The Req object.
  Return value By default values are case sensitive binary strings, however constraints may change the type of this value (for example automatically converting numbers to integer).
Changelog 2.0: Only the values are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:bindings(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.bindings/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.bindings/</guid>
      <description>Name cowboy_req:bindings - Access all values bound from the route
Description bindings(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:bindings()  Return a map containing all bindings.
Arguments Req The Req object.
  Return value By default values are case sensitive binary strings, however constraints may change the type of this value (for example automatically converting numbers to integer).
Changelog 2.0: Only the values are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:bindings(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.bindings/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.bindings/</guid>
      <description>Name cowboy_req:bindings - Access all values bound from the route
Description bindings(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:bindings()  Return a map containing all bindings.
Arguments Req The Req object.
  Return value By default values are case sensitive binary strings, however constraints may change the type of this value (for example automatically converting numbers to integer).
Changelog 2.0: Only the values are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:bindings(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.bindings/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.bindings/</guid>
      <description>Name cowboy_req:bindings - Access all values bound from the route
Description bindings(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:bindings()  Return a map containing all bindings.
Arguments Req The Req object.
  Return value By default values are case sensitive binary strings, however constraints may change the type of this value (for example automatically converting numbers to integer).
Changelog 2.0: Only the values are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:body_length(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.body_length/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.body_length/</guid>
      <description>Name cowboy_req:body_length - Body length
Description body_length(Req :: cowboy_req:req()) -&amp;gt; undefined | non_neg_integer()  Return the length of the request body.
The length is not always known before reading the body. In those cases Cowboy will return undefined. The body length is available after the body has been fully read.
Arguments Req The Req object.
  Return value The length of the request body, or undefined if it is not known.</description>
    </item>
    
    <item>
      <title>cowboy_req:body_length(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.body_length/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.body_length/</guid>
      <description>Name cowboy_req:body_length - Body length
Description body_length(Req :: cowboy_req:req()) -&amp;gt; undefined | non_neg_integer()  Return the length of the request body.
The length is not always known before reading the body. In those cases Cowboy will return undefined. The body length is available after the body has been fully read.
Arguments Req The Req object.
  Return value The length of the request body, or undefined if it is not known.</description>
    </item>
    
    <item>
      <title>cowboy_req:body_length(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.body_length/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.body_length/</guid>
      <description>Name cowboy_req:body_length - Body length
Description body_length(Req :: cowboy_req:req()) -&amp;gt; undefined | non_neg_integer()  Return the length of the request body.
The length is not always known before reading the body. In those cases Cowboy will return undefined. The body length is available after the body has been fully read.
Arguments Req The Req object.
  Return value The length of the request body, or undefined if it is not known.</description>
    </item>
    
    <item>
      <title>cowboy_req:body_length(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.body_length/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.body_length/</guid>
      <description>Name cowboy_req:body_length - Body length
Description body_length(Req :: cowboy_req:req()) -&amp;gt; undefined | non_neg_integer()  Return the length of the request body.
The length is not always known before reading the body. In those cases Cowboy will return undefined. The body length is available after the body has been fully read.
Arguments Req The Req object.
  Return value The length of the request body, or undefined if it is not known.</description>
    </item>
    
    <item>
      <title>cowboy_req:body_length(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.body_length/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.body_length/</guid>
      <description>Name cowboy_req:body_length - Body length
Description body_length(Req :: cowboy_req:req()) -&amp;gt; undefined | non_neg_integer()  Return the length of the request body.
The length is not always known before reading the body. In those cases Cowboy will return undefined. The body length is available after the body has been fully read.
Arguments Req The Req object.
  Return value The length of the request body, or undefined if it is not known.</description>
    </item>
    
    <item>
      <title>cowboy_req:body_length(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.body_length/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.body_length/</guid>
      <description>Name cowboy_req:body_length - Body length
Description body_length(Req :: cowboy_req:req()) -&amp;gt; undefined | non_neg_integer()  Return the length of the request body.
The length is not always known before reading the body. In those cases Cowboy will return undefined. The body length is available after the body has been fully read.
Arguments Req The Req object.
  Return value The length of the request body, or undefined if it is not known.</description>
    </item>
    
    <item>
      <title>cowboy_req:cast(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.cast/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.cast/</guid>
      <description>Name cowboy_req:cast - Cast a stream handler event
Description cast(Event :: any(), Req :: cowboy_req:req()) -&amp;gt; ok  Cast a stream handler event.
The event will be passed to stream handlers through the info/3 callback.
Arguments Event The event to be sent to stream handlers.
 Req The Req object.
  Return value The atom ok is always returned. It can be safely ignored.
Changelog 2.7: Function introduced.   Examples Increase the HTTP/1.</description>
    </item>
    
    <item>
      <title>cowboy_req:cert(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.cert/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.cert/</guid>
      <description>Name cowboy_req:cert - Client TLS certificate
Description cert(Req :: cowboy_req:req()) -&amp;gt; binary() | undefined  Return the peer&amp;apos;s TLS certificate.
Using the default configuration this function will always return undefined. You need to explicitly configure Cowboy to request the client certificate. To do this you need to set the verify transport option to verify_peer:
{ok, _} = cowboy:start_tls(example, [ {port, 8443}, {cert, &#34;path/to/cert.pem&#34;}, {verify, verify_peer} ], #{ env =&amp;gt; #{dispatch =&amp;gt; Dispatch} }).</description>
    </item>
    
    <item>
      <title>cowboy_req:cert(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.cert/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.cert/</guid>
      <description>Name cowboy_req:cert - Client TLS certificate
Description cert(Req :: cowboy_req:req()) -&amp;gt; binary() | undefined  Return the peer&amp;apos;s TLS certificate.
Using the default configuration this function will always return undefined. You need to explicitly configure Cowboy to request the client certificate. To do this you need to set the verify transport option to verify_peer:
{ok, _} = cowboy:start_tls(example, [ {port, 8443}, {cert, &#34;path/to/cert.pem&#34;}, {verify, verify_peer} ], #{ env =&amp;gt; #{dispatch =&amp;gt; Dispatch} }).</description>
    </item>
    
    <item>
      <title>cowboy_req:cert(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.cert/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.cert/</guid>
      <description>Name cowboy_req:cert - Client TLS certificate
Description cert(Req :: cowboy_req:req()) -&amp;gt; binary() | undefined  Return the peer&amp;apos;s TLS certificate.
Using the default configuration this function will always return undefined. You need to explicitly configure Cowboy to request the client certificate. To do this you need to set the verify transport option to verify_peer:
{ok, _} = cowboy:start_tls(example, [ {port, 8443}, {cert, &#34;path/to/cert.pem&#34;}, {verify, verify_peer} ], #{ env =&amp;gt; #{dispatch =&amp;gt; Dispatch} }).</description>
    </item>
    
    <item>
      <title>cowboy_req:cert(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.cert/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.cert/</guid>
      <description>Name cowboy_req:cert - Client TLS certificate
Description cert(Req :: cowboy_req:req()) -&amp;gt; binary() | undefined  Return the peer&amp;apos;s TLS certificate.
Using the default configuration this function will always return undefined. You need to explicitly configure Cowboy to request the client certificate. To do this you need to set the verify transport option to verify_peer:
{ok, _} = cowboy:start_tls(example, [ {port, 8443}, {cert, &#34;path/to/cert.pem&#34;}, {verify, verify_peer} ], #{ env =&amp;gt; #{dispatch =&amp;gt; Dispatch} }).</description>
    </item>
    
    <item>
      <title>cowboy_req:cert(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.cert/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.cert/</guid>
      <description>Name cowboy_req:cert - Client TLS certificate
Description cert(Req :: cowboy_req:req()) -&amp;gt; binary() | undefined  Return the peer&amp;apos;s TLS certificate.
Using the default configuration this function will always return undefined. You need to explicitly configure Cowboy to request the client certificate. To do this you need to set the verify transport option to verify_peer:
{ok, _} = cowboy:start_tls(example, [ {port, 8443}, {cert, &#34;path/to/cert.pem&#34;}, {verify, verify_peer} ], #{ env =&amp;gt; #{dispatch =&amp;gt; Dispatch} }).</description>
    </item>
    
    <item>
      <title>cowboy_req:cert(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.cert/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.cert/</guid>
      <description>Name cowboy_req:cert - Client TLS certificate
Description cert(Req :: cowboy_req:req()) -&amp;gt; binary() | undefined  Return the peer&amp;apos;s TLS certificate.
Using the default configuration this function will always return undefined. You need to explicitly configure Cowboy to request the client certificate. To do this you need to set the verify transport option to verify_peer:
{ok, _} = cowboy:start_tls(example, [ {port, 8443}, {certfile, &#34;path/to/cert.pem&#34;}, {verify, verify_peer} ], #{ env =&amp;gt; #{dispatch =&amp;gt; Dispatch} }).</description>
    </item>
    
    <item>
      <title>cowboy_req:delete_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.delete_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.delete_resp_header/</guid>
      <description>Name cowboy_req:delete_resp_header - Delete a response header
Description delete_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive  Delete the given response header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Arguments Name Header name as a lowercase binary string.
 Req The Req object.
  Return value A new Req object is returned.</description>
    </item>
    
    <item>
      <title>cowboy_req:delete_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.delete_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.delete_resp_header/</guid>
      <description>Name cowboy_req:delete_resp_header - Delete a response header
Description delete_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive  Delete the given response header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Arguments Name Header name as a lowercase binary string.
 Req The Req object.
  Return value A new Req object is returned.</description>
    </item>
    
    <item>
      <title>cowboy_req:delete_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.delete_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.delete_resp_header/</guid>
      <description>Name cowboy_req:delete_resp_header - Delete a response header
Description delete_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive  Delete the given response header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Arguments Name Header name as a lowercase binary string.
 Req The Req object.
  Return value A new Req object is returned.</description>
    </item>
    
    <item>
      <title>cowboy_req:delete_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.delete_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.delete_resp_header/</guid>
      <description>Name cowboy_req:delete_resp_header - Delete a response header
Description delete_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive  Delete the given response header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Arguments Name Header name as a lowercase binary string.
 Req The Req object.
  Return value A new Req object is returned.</description>
    </item>
    
    <item>
      <title>cowboy_req:delete_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.delete_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.delete_resp_header/</guid>
      <description>Name cowboy_req:delete_resp_header - Delete a response header
Description delete_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive  Delete the given response header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Arguments Name Header name as a lowercase binary string.
 Req The Req object.
  Return value A new Req object is returned.</description>
    </item>
    
    <item>
      <title>cowboy_req:delete_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.delete_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.delete_resp_header/</guid>
      <description>Name cowboy_req:delete_resp_header - Delete a response header
Description delete_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive  Delete the given response header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Arguments Name Header name as a lowercase binary string.
 Req The Req object.
  Return value A new Req object is returned.</description>
    </item>
    
    <item>
      <title>cowboy_req:filter_cookies(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.filter_cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.filter_cookies/</guid>
      <description>Name cowboy_req:filter_cookies - Filter cookie headers
Description filter_cookies(Names, Req) -&amp;gt; Req Names :: [atom() | binary()]  Filter cookie headers.
This function is meant to be used before attempting to parse or match cookies in order to remove cookies that are not relevant and are potentially malformed. Because Cowboy by default crashes on malformed cookies, this function allows processing requests that would otherwise result in a 400 error.
Malformed cookies are unfortunately fairly common due to the string-based interface provided by browsers and this function provides a middle ground between Cowboy&amp;apos;s strict behavior and chaotic real world use cases.</description>
    </item>
    
    <item>
      <title>cowboy_req:has_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.has_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.has_body/</guid>
      <description>Name cowboy_req:has_body - Is there a request body?
Description has_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether the request has a body.
Arguments Req The Req object.
  Return value A boolean indicating whether the request has a body.
Changelog 1.0: Function introduced.   Examples Ensure the request has a body true = cowboy_req:has_body(Req).  See also cowboy_req(3), cowboy_req:body_length(3), cowboy_req:read_body(3), cowboy_req:read_urlencoded_body(3), cowboy_req:read_part(3), cowboy_req:read_part_body(3)</description>
    </item>
    
    <item>
      <title>cowboy_req:has_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.has_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.has_body/</guid>
      <description>Name cowboy_req:has_body - Is there a request body?
Description has_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether the request has a body.
Arguments Req The Req object.
  Return value A boolean indicating whether the request has a body.
Changelog 1.0: Function introduced.   Examples Ensure the request has a body true = cowboy_req:has_body(Req).  See also cowboy_req(3), cowboy_req:body_length(3), cowboy_req:read_body(3), cowboy_req:read_urlencoded_body(3), cowboy_req:read_part(3), cowboy_req:read_part_body(3)</description>
    </item>
    
    <item>
      <title>cowboy_req:has_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.has_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.has_body/</guid>
      <description>Name cowboy_req:has_body - Is there a request body?
Description has_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether the request has a body.
Arguments Req The Req object.
  Return value A boolean indicating whether the request has a body.
Changelog 1.0: Function introduced.   Examples Ensure the request has a body true = cowboy_req:has_body(Req).  See also cowboy_req(3), cowboy_req:body_length(3), cowboy_req:read_body(3), cowboy_req:read_urlencoded_body(3), cowboy_req:read_part(3), cowboy_req:read_part_body(3)</description>
    </item>
    
    <item>
      <title>cowboy_req:has_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.has_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.has_body/</guid>
      <description>Name cowboy_req:has_body - Is there a request body?
Description has_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether the request has a body.
Arguments Req The Req object.
  Return value A boolean indicating whether the request has a body.
Changelog 1.0: Function introduced.   Examples Ensure the request has a body true = cowboy_req:has_body(Req).  See also cowboy_req(3), cowboy_req:body_length(3), cowboy_req:read_body(3), cowboy_req:read_urlencoded_body(3), cowboy_req:read_part(3), cowboy_req:read_part_body(3)</description>
    </item>
    
    <item>
      <title>cowboy_req:has_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.has_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.has_body/</guid>
      <description>Name cowboy_req:has_body - Is there a request body?
Description has_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether the request has a body.
Arguments Req The Req object.
  Return value A boolean indicating whether the request has a body.
Changelog 1.0: Function introduced.   Examples Ensure the request has a body true = cowboy_req:has_body(Req).  See also cowboy_req(3), cowboy_req:body_length(3), cowboy_req:read_body(3), cowboy_req:read_urlencoded_body(3), cowboy_req:read_part(3), cowboy_req:read_part_body(3)</description>
    </item>
    
    <item>
      <title>cowboy_req:has_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.has_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.has_body/</guid>
      <description>Name cowboy_req:has_body - Is there a request body?
Description has_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether the request has a body.
Arguments Req The Req object.
  Return value A boolean indicating whether the request has a body.
Changelog 1.0: Function introduced.   Examples Ensure the request has a body true = cowboy_req:has_body(Req).  See also cowboy_req(3), cowboy_req:body_length(3), cowboy_req:read_body(3), cowboy_req:read_urlencoded_body(3), cowboy_req:read_part(3), cowboy_req:read_part_body(3)</description>
    </item>
    
    <item>
      <title>cowboy_req:has_resp_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.has_resp_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.has_resp_body/</guid>
      <description>Name cowboy_req:has_resp_body - Is there a response body?
Description has_resp_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether a response body has been set.
Arguments Req The Req object.
  Return value A boolean indicating whether a response body has been set.
This function will return false when an empty response body has been set.
Changelog 1.0: Function introduced.   Examples Check whether a body has been set false = cowboy_req:has_resp_body(Req0), Req1 = cowboy_req:set_resp_body(&amp;lt;&amp;lt;&#34;</description>
    </item>
    
    <item>
      <title>cowboy_req:has_resp_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.has_resp_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.has_resp_body/</guid>
      <description>Name cowboy_req:has_resp_body - Is there a response body?
Description has_resp_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether a response body has been set.
Arguments Req The Req object.
  Return value A boolean indicating whether a response body has been set.
This function will return false when an empty response body has been set.
Changelog 1.0: Function introduced.   Examples Check whether a body has been set false = cowboy_req:has_resp_body(Req0), Req1 = cowboy_req:set_resp_body(&amp;lt;&amp;lt;&#34;</description>
    </item>
    
    <item>
      <title>cowboy_req:has_resp_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.has_resp_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.has_resp_body/</guid>
      <description>Name cowboy_req:has_resp_body - Is there a response body?
Description has_resp_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether a response body has been set.
Arguments Req The Req object.
  Return value A boolean indicating whether a response body has been set.
This function will return false when an empty response body has been set.
Changelog 1.0: Function introduced.   Examples Check whether a body has been set false = cowboy_req:has_resp_body(Req0), Req1 = cowboy_req:set_resp_body(&amp;lt;&amp;lt;&#34;</description>
    </item>
    
    <item>
      <title>cowboy_req:has_resp_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.has_resp_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.has_resp_body/</guid>
      <description>Name cowboy_req:has_resp_body - Is there a response body?
Description has_resp_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether a response body has been set.
Arguments Req The Req object.
  Return value A boolean indicating whether a response body has been set.
This function will return false when an empty response body has been set.
Changelog 1.0: Function introduced.   Examples Check whether a body has been set false = cowboy_req:has_resp_body(Req0), Req1 = cowboy_req:set_resp_body(&amp;lt;&amp;lt;&#34;</description>
    </item>
    
    <item>
      <title>cowboy_req:has_resp_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.has_resp_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.has_resp_body/</guid>
      <description>Name cowboy_req:has_resp_body - Is there a response body?
Description has_resp_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether a response body has been set.
Arguments Req The Req object.
  Return value A boolean indicating whether a response body has been set.
This function will return false when an empty response body has been set.
Changelog 1.0: Function introduced.   Examples Check whether a body has been set false = cowboy_req:has_resp_body(Req0), Req1 = cowboy_req:set_resp_body(&amp;lt;&amp;lt;&#34;</description>
    </item>
    
    <item>
      <title>cowboy_req:has_resp_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.has_resp_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.has_resp_body/</guid>
      <description>Name cowboy_req:has_resp_body - Is there a response body?
Description has_resp_body(Req :: cowboy_req:req()) -&amp;gt; boolean()  Return whether a response body has been set.
Arguments Req The Req object.
  Return value A boolean indicating whether a response body has been set.
This function will return false when an empty response body has been set.
Changelog 1.0: Function introduced.   Examples Check whether a body has been set false = cowboy_req:has_resp_body(Req0), Req1 = cowboy_req:set_resp_body(&amp;lt;&amp;lt;&#34;</description>
    </item>
    
    <item>
      <title>cowboy_req:has_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.has_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.has_resp_header/</guid>
      <description>Name cowboy_req:has_resp_header - Is the given response header set?
Description has_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; boolean() Name :: binary() %% lowercase; case insensitive  Return whether the given response header has been set.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Arguments Name Header name as a lowercase binary string.</description>
    </item>
    
    <item>
      <title>cowboy_req:has_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.has_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.has_resp_header/</guid>
      <description>Name cowboy_req:has_resp_header - Is the given response header set?
Description has_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; boolean() Name :: binary() %% lowercase; case insensitive  Return whether the given response header has been set.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Arguments Name Header name as a lowercase binary string.</description>
    </item>
    
    <item>
      <title>cowboy_req:has_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.has_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.has_resp_header/</guid>
      <description>Name cowboy_req:has_resp_header - Is the given response header set?
Description has_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; boolean() Name :: binary() %% lowercase; case insensitive  Return whether the given response header has been set.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Arguments Name Header name as a lowercase binary string.</description>
    </item>
    
    <item>
      <title>cowboy_req:has_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.has_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.has_resp_header/</guid>
      <description>Name cowboy_req:has_resp_header - Is the given response header set?
Description has_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; boolean() Name :: binary() %% lowercase; case insensitive  Return whether the given response header has been set.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Arguments Name Header name as a lowercase binary string.</description>
    </item>
    
    <item>
      <title>cowboy_req:has_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.has_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.has_resp_header/</guid>
      <description>Name cowboy_req:has_resp_header - Is the given response header set?
Description has_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; boolean() Name :: binary() %% lowercase; case insensitive  Return whether the given response header has been set.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Arguments Name Header name as a lowercase binary string.</description>
    </item>
    
    <item>
      <title>cowboy_req:has_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.has_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.has_resp_header/</guid>
      <description>Name cowboy_req:has_resp_header - Is the given response header set?
Description has_resp_header(Name, Req :: cowboy_req:req()) -&amp;gt; boolean() Name :: binary() %% lowercase; case insensitive  Return whether the given response header has been set.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Arguments Name Header name as a lowercase binary string.</description>
    </item>
    
    <item>
      <title>cowboy_req:header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.header/</guid>
      <description>Name cowboy_req:header - HTTP header
Description header(Name, Req) -&amp;gt; header(Name, Req, undefined) header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given HTTP header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Headers can also be obtained using pattern matching:</description>
    </item>
    
    <item>
      <title>cowboy_req:header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.header/</guid>
      <description>Name cowboy_req:header - HTTP header
Description header(Name, Req) -&amp;gt; header(Name, Req, undefined) header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given HTTP header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Headers can also be obtained using pattern matching:</description>
    </item>
    
    <item>
      <title>cowboy_req:header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.header/</guid>
      <description>Name cowboy_req:header - HTTP header
Description header(Name, Req) -&amp;gt; header(Name, Req, undefined) header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given HTTP header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Headers can also be obtained using pattern matching:</description>
    </item>
    
    <item>
      <title>cowboy_req:header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.header/</guid>
      <description>Name cowboy_req:header - HTTP header
Description header(Name, Req) -&amp;gt; header(Name, Req, undefined) header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given HTTP header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Headers can also be obtained using pattern matching:</description>
    </item>
    
    <item>
      <title>cowboy_req:header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.header/</guid>
      <description>Name cowboy_req:header - HTTP header
Description header(Name, Req) -&amp;gt; header(Name, Req, undefined) header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given HTTP header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Headers can also be obtained using pattern matching:</description>
    </item>
    
    <item>
      <title>cowboy_req:header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.header/</guid>
      <description>Name cowboy_req:header - HTTP header
Description header(Name, Req) -&amp;gt; header(Name, Req, undefined) header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given HTTP header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Headers can also be obtained using pattern matching:</description>
    </item>
    
    <item>
      <title>cowboy_req:headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.headers/</guid>
      <description>Name cowboy_req:headers - HTTP headers
Description headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all request headers.
Request headers can also be obtained using pattern matching:
#{headers := Headers} = Req.  Arguments Req The Req object.
  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
Changelog 2.0: Only the headers are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.headers/</guid>
      <description>Name cowboy_req:headers - HTTP headers
Description headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all request headers.
Request headers can also be obtained using pattern matching:
#{headers := Headers} = Req.  Arguments Req The Req object.
  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
Changelog 2.0: Only the headers are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.headers/</guid>
      <description>Name cowboy_req:headers - HTTP headers
Description headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all request headers.
Request headers can also be obtained using pattern matching:
#{headers := Headers} = Req.  Arguments Req The Req object.
  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
Changelog 2.0: Only the headers are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.headers/</guid>
      <description>Name cowboy_req:headers - HTTP headers
Description headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all request headers.
Request headers can also be obtained using pattern matching:
#{headers := Headers} = Req.  Arguments Req The Req object.
  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
Changelog 2.0: Only the headers are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.headers/</guid>
      <description>Name cowboy_req:headers - HTTP headers
Description headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all request headers.
Request headers can also be obtained using pattern matching:
#{headers := Headers} = Req.  Arguments Req The Req object.
  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
Changelog 2.0: Only the headers are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.headers/</guid>
      <description>Name cowboy_req:headers - HTTP headers
Description headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all request headers.
Request headers can also be obtained using pattern matching:
#{headers := Headers} = Req.  Arguments Req The Req object.
  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
Changelog 2.0: Only the headers are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:host(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.host/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.host/</guid>
      <description>Name cowboy_req:host - URI host name
Description host(Req :: cowboy_req:req()) -&amp;gt; Host :: binary()  Return the host name of the effective request URI.
The host name can also be obtained using pattern matching:
#{host := Host} = Req.  Arguments Req The Req object.
  Return value The host name is returned as a lowercase binary string. It is case insensitive.
Changelog 2.0: Only the host name is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:host(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.host/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.host/</guid>
      <description>Name cowboy_req:host - URI host name
Description host(Req :: cowboy_req:req()) -&amp;gt; Host :: binary()  Return the host name of the effective request URI.
The host name can also be obtained using pattern matching:
#{host := Host} = Req.  Arguments Req The Req object.
  Return value The host name is returned as a lowercase binary string. It is case insensitive.
Changelog 2.0: Only the host name is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:host(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.host/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.host/</guid>
      <description>Name cowboy_req:host - URI host name
Description host(Req :: cowboy_req:req()) -&amp;gt; Host :: binary()  Return the host name of the effective request URI.
The host name can also be obtained using pattern matching:
#{host := Host} = Req.  Arguments Req The Req object.
  Return value The host name is returned as a lowercase binary string. It is case insensitive.
Changelog 2.0: Only the host name is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:host(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.host/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.host/</guid>
      <description>Name cowboy_req:host - URI host name
Description host(Req :: cowboy_req:req()) -&amp;gt; Host :: binary()  Return the host name of the effective request URI.
The host name can also be obtained using pattern matching:
#{host := Host} = Req.  Arguments Req The Req object.
  Return value The host name is returned as a lowercase binary string. It is case insensitive.
Changelog 2.0: Only the host name is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:host(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.host/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.host/</guid>
      <description>Name cowboy_req:host - URI host name
Description host(Req :: cowboy_req:req()) -&amp;gt; Host :: binary()  Return the host name of the effective request URI.
The host name can also be obtained using pattern matching:
#{host := Host} = Req.  Arguments Req The Req object.
  Return value The host name is returned as a lowercase binary string. It is case insensitive.
Changelog 2.0: Only the host name is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:host(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.host/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.host/</guid>
      <description>Name cowboy_req:host - URI host name
Description host(Req :: cowboy_req:req()) -&amp;gt; Host :: binary()  Return the host name of the effective request URI.
The host name can also be obtained using pattern matching:
#{host := Host} = Req.  Arguments Req The Req object.
  Return value The host name is returned as a lowercase binary string. It is case insensitive.
Changelog 2.0: Only the host name is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:host_info(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.host_info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.host_info/</guid>
      <description>Name cowboy_req:host_info - Access the route&amp;apos;s heading host segments
Description host_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the heading host segments.
This is the part of the host name that was matched using the ... notation.
Arguments Req The Req object.
  Return value The tokens are returned as a list of case insensitive binary strings.
Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:host_info(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.host_info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.host_info/</guid>
      <description>Name cowboy_req:host_info - Access the route&amp;apos;s heading host segments
Description host_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the heading host segments.
This is the part of the host name that was matched using the ... notation.
Arguments Req The Req object.
  Return value The tokens are returned as a list of case insensitive binary strings.
Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:host_info(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.host_info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.host_info/</guid>
      <description>Name cowboy_req:host_info - Access the route&amp;apos;s heading host segments
Description host_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the heading host segments.
This is the part of the host name that was matched using the ... notation.
Arguments Req The Req object.
  Return value The tokens are returned as a list of case insensitive binary strings.
Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:host_info(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.host_info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.host_info/</guid>
      <description>Name cowboy_req:host_info - Access the route&amp;apos;s heading host segments
Description host_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the heading host segments.
This is the part of the host name that was matched using the ... notation.
Arguments Req The Req object.
  Return value The tokens are returned as a list of case insensitive binary strings.
Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:host_info(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.host_info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.host_info/</guid>
      <description>Name cowboy_req:host_info - Access the route&amp;apos;s heading host segments
Description host_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the heading host segments.
This is the part of the host name that was matched using the ... notation.
Arguments Req The Req object.
  Return value The tokens are returned as a list of case insensitive binary strings.
Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:host_info(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.host_info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.host_info/</guid>
      <description>Name cowboy_req:host_info - Access the route&amp;apos;s heading host segments
Description host_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the heading host segments.
This is the part of the host name that was matched using the ... notation.
Arguments Req The Req object.
  Return value The tokens are returned as a list of case insensitive binary strings.
Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:inform(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.inform/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.inform/</guid>
      <description>Name cowboy_req:inform - Send an informational response
Description inform(Status, Req :: cowboy_req:req()) -&amp;gt; inform(StatusCode, #{}, Req) inform(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; ok Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send an informational response.
Informational responses use a status code between 100 and 199. They cannot include a body. This function will not use any of the previously set headers. All headers to be sent must be given directly.
Any number of informational responses can be sent as long as they are sent before the proper response.</description>
    </item>
    
    <item>
      <title>cowboy_req:inform(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.inform/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.inform/</guid>
      <description>Name cowboy_req:inform - Send an informational response
Description inform(Status, Req :: cowboy_req:req()) -&amp;gt; inform(StatusCode, #{}, Req) inform(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; ok Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send an informational response.
Informational responses use a status code between 100 and 199. They cannot include a body. This function will not use any of the previously set headers. All headers to be sent must be given directly.
Any number of informational responses can be sent as long as they are sent before the proper response.</description>
    </item>
    
    <item>
      <title>cowboy_req:inform(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.inform/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.inform/</guid>
      <description>Name cowboy_req:inform - Send an informational response
Description inform(Status, Req :: cowboy_req:req()) -&amp;gt; inform(StatusCode, #{}, Req) inform(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; ok Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send an informational response.
Informational responses use a status code between 100 and 199. They cannot include a body. This function will not use any of the previously set headers. All headers to be sent must be given directly.
Any number of informational responses can be sent as long as they are sent before the proper response.</description>
    </item>
    
    <item>
      <title>cowboy_req:inform(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.inform/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.inform/</guid>
      <description>Name cowboy_req:inform - Send an informational response
Description inform(Status, Req :: cowboy_req:req()) -&amp;gt; inform(StatusCode, #{}, Req) inform(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; ok Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send an informational response.
Informational responses use a status code between 100 and 199. They cannot include a body. This function will not use any of the previously set headers. All headers to be sent must be given directly.
Any number of informational responses can be sent as long as they are sent before the proper response.</description>
    </item>
    
    <item>
      <title>cowboy_req:inform(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.inform/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.inform/</guid>
      <description>Name cowboy_req:inform - Send an informational response
Description inform(Status, Req :: cowboy_req:req()) -&amp;gt; inform(StatusCode, #{}, Req) inform(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; ok Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send an informational response.
Informational responses use a status code between 100 and 199. They cannot include a body. This function will not use any of the previously set headers. All headers to be sent must be given directly.
Any number of informational responses can be sent as long as they are sent before the proper response.</description>
    </item>
    
    <item>
      <title>cowboy_req:inform(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.inform/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.inform/</guid>
      <description>Name cowboy_req:inform - Send an informational response
Description inform(Status, Req :: cowboy_req:req()) -&amp;gt; inform(StatusCode, #{}, Req) inform(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; ok Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send an informational response.
Informational responses use a status code between 100 and 199. They cannot include a body. This function will not use any of the previously set headers. All headers to be sent must be given directly.
Any number of informational responses can be sent as long as they are sent before the proper response.</description>
    </item>
    
    <item>
      <title>cowboy_req:match_cookies(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.match_cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.match_cookies/</guid>
      <description>Name cowboy_req:match_cookies - Match cookies against constraints
Description match_cookies(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the cookies and match specific values against constraints.
Cowboy will only return the cookie values specified in the fields list, and ignore all others. Fields can be either the name of the cookie requested; the name along with a list of constraints; or the name, a list of constraints and a default value in case the cookie is missing.</description>
    </item>
    
    <item>
      <title>cowboy_req:match_cookies(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.match_cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.match_cookies/</guid>
      <description>Name cowboy_req:match_cookies - Match cookies against constraints
Description match_cookies(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the cookies and match specific values against constraints.
Cowboy will only return the cookie values specified in the fields list, and ignore all others. Fields can be either the name of the cookie requested; the name along with a list of constraints; or the name, a list of constraints and a default value in case the cookie is missing.</description>
    </item>
    
    <item>
      <title>cowboy_req:match_cookies(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.match_cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.match_cookies/</guid>
      <description>Name cowboy_req:match_cookies - Match cookies against constraints
Description match_cookies(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the cookies and match specific values against constraints.
Cowboy will only return the cookie values specified in the fields list, and ignore all others. Fields can be either the name of the cookie requested; the name along with a list of constraints; or the name, a list of constraints and a default value in case the cookie is missing.</description>
    </item>
    
    <item>
      <title>cowboy_req:match_cookies(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.match_cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.match_cookies/</guid>
      <description>Name cowboy_req:match_cookies - Match cookies against constraints
Description match_cookies(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the cookies and match specific values against constraints.
Cowboy will only return the cookie values specified in the fields list, and ignore all others. Fields can be either the name of the cookie requested; the name along with a list of constraints; or the name, a list of constraints and a default value in case the cookie is missing.</description>
    </item>
    
    <item>
      <title>cowboy_req:match_cookies(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.match_cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.match_cookies/</guid>
      <description>Name cowboy_req:match_cookies - Match cookies against constraints
Description match_cookies(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the cookies and match specific values against constraints.
Cowboy will only return the cookie values specified in the fields list, and ignore all others. Fields can be either the name of the cookie requested; the name along with a list of constraints; or the name, a list of constraints and a default value in case the cookie is missing.</description>
    </item>
    
    <item>
      <title>cowboy_req:match_cookies(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.match_cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.match_cookies/</guid>
      <description>Name cowboy_req:match_cookies - Match cookies against constraints
Description match_cookies(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the cookies and match specific values against constraints.
Cowboy will only return the cookie values specified in the fields list, and ignore all others. Fields can be either the name of the cookie requested; the name along with a list of constraints; or the name, a list of constraints and a default value in case the cookie is missing.</description>
    </item>
    
    <item>
      <title>cowboy_req:match_qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.match_qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.match_qs/</guid>
      <description>Name cowboy_req:match_qs - Match the query string against constraints
Description match_qs(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the query string and match specific values against constraints.
Cowboy will only return the query string values specified in the fields list, and ignore all others. Fields can be either the key requested; the key along with a list of constraints; or the key, a list of constraints and a default value in case the key is missing.</description>
    </item>
    
    <item>
      <title>cowboy_req:match_qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.match_qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.match_qs/</guid>
      <description>Name cowboy_req:match_qs - Match the query string against constraints
Description match_qs(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the query string and match specific values against constraints.
Cowboy will only return the query string values specified in the fields list, and ignore all others. Fields can be either the key requested; the key along with a list of constraints; or the key, a list of constraints and a default value in case the key is missing.</description>
    </item>
    
    <item>
      <title>cowboy_req:match_qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.match_qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.match_qs/</guid>
      <description>Name cowboy_req:match_qs - Match the query string against constraints
Description match_qs(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the query string and match specific values against constraints.
Cowboy will only return the query string values specified in the fields list, and ignore all others. Fields can be either the key requested; the key along with a list of constraints; or the key, a list of constraints and a default value in case the key is missing.</description>
    </item>
    
    <item>
      <title>cowboy_req:match_qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.match_qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.match_qs/</guid>
      <description>Name cowboy_req:match_qs - Match the query string against constraints
Description match_qs(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the query string and match specific values against constraints.
Cowboy will only return the query string values specified in the fields list, and ignore all others. Fields can be either the key requested; the key along with a list of constraints; or the key, a list of constraints and a default value in case the key is missing.</description>
    </item>
    
    <item>
      <title>cowboy_req:match_qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.match_qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.match_qs/</guid>
      <description>Name cowboy_req:match_qs - Match the query string against constraints
Description match_qs(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the query string and match specific values against constraints.
Cowboy will only return the query string values specified in the fields list, and ignore all others. Fields can be either the key requested; the key along with a list of constraints; or the key, a list of constraints and a default value in case the key is missing.</description>
    </item>
    
    <item>
      <title>cowboy_req:match_qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.match_qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.match_qs/</guid>
      <description>Name cowboy_req:match_qs - Match the query string against constraints
Description match_qs(Fields :: cowboy:fields(), Req :: cowboy_req:req()) -&amp;gt; #{atom() =&amp;gt; any()}  Parse the query string and match specific values against constraints.
Cowboy will only return the query string values specified in the fields list, and ignore all others. Fields can be either the key requested; the key along with a list of constraints; or the key, a list of constraints and a default value in case the key is missing.</description>
    </item>
    
    <item>
      <title>cowboy_req:method(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.method/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.method/</guid>
      <description>Name cowboy_req:method - HTTP method
Description method(Req :: cowboy_req:req()) -&amp;gt; Method :: binary()  Return the request&amp;apos;s HTTP method.
The method can also be obtained using pattern matching:
#{method := Method} = Req.  Arguments Req The Req object.
  Return value The request&amp;apos;s HTTP method is returned as a binary string. While methods are case sensitive, standard methods are always uppercase.
Changelog 2.0: Only the method is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:method(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.method/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.method/</guid>
      <description>Name cowboy_req:method - HTTP method
Description method(Req :: cowboy_req:req()) -&amp;gt; Method :: binary()  Return the request&amp;apos;s HTTP method.
The method can also be obtained using pattern matching:
#{method := Method} = Req.  Arguments Req The Req object.
  Return value The request&amp;apos;s HTTP method is returned as a binary string. While methods are case sensitive, standard methods are always uppercase.
Changelog 2.0: Only the method is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:method(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.method/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.method/</guid>
      <description>Name cowboy_req:method - HTTP method
Description method(Req :: cowboy_req:req()) -&amp;gt; Method :: binary()  Return the request&amp;apos;s HTTP method.
The method can also be obtained using pattern matching:
#{method := Method} = Req.  Arguments Req The Req object.
  Return value The request&amp;apos;s HTTP method is returned as a binary string. While methods are case sensitive, standard methods are always uppercase.
Changelog 2.0: Only the method is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:method(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.method/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.method/</guid>
      <description>Name cowboy_req:method - HTTP method
Description method(Req :: cowboy_req:req()) -&amp;gt; Method :: binary()  Return the request&amp;apos;s HTTP method.
The method can also be obtained using pattern matching:
#{method := Method} = Req.  Arguments Req The Req object.
  Return value The request&amp;apos;s HTTP method is returned as a binary string. While methods are case sensitive, standard methods are always uppercase.
Changelog 2.0: Only the method is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:method(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.method/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.method/</guid>
      <description>Name cowboy_req:method - HTTP method
Description method(Req :: cowboy_req:req()) -&amp;gt; Method :: binary()  Return the request&amp;apos;s HTTP method.
The method can also be obtained using pattern matching:
#{method := Method} = Req.  Arguments Req The Req object.
  Return value The request&amp;apos;s HTTP method is returned as a binary string. While methods are case sensitive, standard methods are always uppercase.
Changelog 2.0: Only the method is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:method(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.method/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.method/</guid>
      <description>Name cowboy_req:method - HTTP method
Description method(Req :: cowboy_req:req()) -&amp;gt; Method :: binary()  Return the request&amp;apos;s HTTP method.
The method can also be obtained using pattern matching:
#{method := Method} = Req.  Arguments Req The Req object.
  Return value The request&amp;apos;s HTTP method is returned as a binary string. While methods are case sensitive, standard methods are always uppercase.
Changelog 2.0: Only the method is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_cookies(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.parse_cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.parse_cookies/</guid>
      <description>Name cowboy_req:parse_cookies - Parse cookie headers
Description parse_cookies(Req) -&amp;gt; [{Name, Value}] Name :: binary() %% case sensitive Value :: binary() %% case sensitive  Parse cookie headers.
Alias for cowboy_req:parse_header(&amp;lt;&amp;lt;&amp;quot;cookie&amp;quot;&amp;gt;&amp;gt;, Req).
When the cookie header is missing, [] is returned.
While an empty cookie header is not valid, some clients do send it. Cowboy will in this case also return [].
Arguments Req The Req object.
  Return value The cookies are returned as a list of key/values.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_cookies(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.parse_cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.parse_cookies/</guid>
      <description>Name cowboy_req:parse_cookies - Parse cookie headers
Description parse_cookies(Req) -&amp;gt; [{Name, Value}] Name :: binary() %% case sensitive Value :: binary() %% case sensitive  Parse cookie headers.
Alias for cowboy_req:parse_header(&amp;lt;&amp;lt;&amp;quot;cookie&amp;quot;&amp;gt;&amp;gt;, Req).
When the cookie header is missing, [] is returned.
While an empty cookie header is not valid, some clients do send it. Cowboy will in this case also return [].
Arguments Req The Req object.
  Return value The cookies are returned as a list of key/values.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_cookies(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.parse_cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.parse_cookies/</guid>
      <description>Name cowboy_req:parse_cookies - Parse cookie headers
Description parse_cookies(Req) -&amp;gt; [{Name, Value}] Name :: binary() %% case sensitive Value :: binary() %% case sensitive  Parse cookie headers.
Alias for cowboy_req:parse_header(&amp;lt;&amp;lt;&amp;quot;cookie&amp;quot;&amp;gt;&amp;gt;, Req).
When the cookie header is missing, [] is returned.
While an empty cookie header is not valid, some clients do send it. Cowboy will in this case also return [].
Arguments Req The Req object.
  Return value The cookies are returned as a list of key/values.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_cookies(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.parse_cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.parse_cookies/</guid>
      <description>Name cowboy_req:parse_cookies - Parse cookie headers
Description parse_cookies(Req) -&amp;gt; [{Name, Value}] Name :: binary() %% case sensitive Value :: binary() %% case sensitive  Parse cookie headers.
Alias for cowboy_req:parse_header(&amp;lt;&amp;lt;&amp;quot;cookie&amp;quot;&amp;gt;&amp;gt;, Req).
When the cookie header is missing, [] is returned.
While an empty cookie header is not valid, some clients do send it. Cowboy will in this case also return [].
Arguments Req The Req object.
  Return value The cookies are returned as a list of key/values.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_cookies(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.parse_cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.parse_cookies/</guid>
      <description>Name cowboy_req:parse_cookies - Parse cookie headers
Description parse_cookies(Req) -&amp;gt; [{Name, Value}] Name :: binary() %% case sensitive Value :: binary() %% case sensitive  Parse cookie headers.
Alias for cowboy_req:parse_header(&amp;lt;&amp;lt;&amp;quot;cookie&amp;quot;&amp;gt;&amp;gt;, Req).
When the cookie header is missing, [] is returned.
While an empty cookie header is not valid, some clients do send it. Cowboy will in this case also return [].
Arguments Req The Req object.
  Return value The cookies are returned as a list of key/values.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_cookies(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.parse_cookies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.parse_cookies/</guid>
      <description>Name cowboy_req:parse_cookies - Parse cookie headers
Description parse_cookies(Req) -&amp;gt; [{Name, Value}] Name :: binary() %% case sensitive Value :: binary() %% case sensitive  Parse cookie headers.
Alias for cowboy_req:parse_header(&amp;lt;&amp;lt;&amp;quot;cookie&amp;quot;&amp;gt;&amp;gt;, Req).
When the cookie header is missing or empty, [] is returned.
This function will crash on invalid cookie data. Because invalid cookies are fairly common when dealing with browsers (because of the string interface that the Javascript API provides), it is recommended to filter the cookie header value before attempting to parse it.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.parse_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.parse_header/</guid>
      <description>Name cowboy_req:parse_header - Parse the given HTTP header
Description parse_header(Name, Req) -&amp;gt; ParsedValue | Default parse_header(Name, Req, Default) -&amp;gt; ParsedValue | Default Name :: binary() Req :: cowboy_req:req() ParsedValue :: any() Default :: any()  Parse the given HTTP header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
The type of the parsed value varies depending on the header.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.parse_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.parse_header/</guid>
      <description>Name cowboy_req:parse_header - Parse the given HTTP header
Description parse_header(Name, Req) -&amp;gt; ParsedValue | Default parse_header(Name, Req, Default) -&amp;gt; ParsedValue | Default Name :: binary() Req :: cowboy_req:req() ParsedValue :: any() Default :: any()  Parse the given HTTP header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
The type of the parsed value varies depending on the header.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.parse_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.parse_header/</guid>
      <description>Name cowboy_req:parse_header - Parse the given HTTP header
Description parse_header(Name, Req) -&amp;gt; ParsedValue | Default parse_header(Name, Req, Default) -&amp;gt; ParsedValue | Default Name :: binary() Req :: cowboy_req:req() ParsedValue :: any() Default :: any()  Parse the given HTTP header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
The type of the parsed value varies depending on the header.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.parse_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.parse_header/</guid>
      <description>Name cowboy_req:parse_header - Parse the given HTTP header
Description parse_header(Name, Req) -&amp;gt; ParsedValue | Default parse_header(Name, Req, Default) -&amp;gt; ParsedValue | Default Name :: binary() Req :: cowboy_req:req() ParsedValue :: any() Default :: any()  Parse the given HTTP header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
The type of the parsed value varies depending on the header.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.parse_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.parse_header/</guid>
      <description>Name cowboy_req:parse_header - Parse the given HTTP header
Description parse_header(Name, Req) -&amp;gt; ParsedValue | Default parse_header(Name, Req, Default) -&amp;gt; ParsedValue | Default Name :: binary() Req :: cowboy_req:req() ParsedValue :: any() Default :: any()  Parse the given HTTP header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
The type of the parsed value varies depending on the header.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.parse_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.parse_header/</guid>
      <description>Name cowboy_req:parse_header - Parse the given HTTP header
Description parse_header(Name, Req) -&amp;gt; ParsedValue | Default parse_header(Name, Req, Default) -&amp;gt; ParsedValue | Default Name :: binary() Req :: cowboy_req:req() ParsedValue :: any() Default :: any()  Parse the given HTTP header.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
The type of the parsed value varies depending on the header.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.parse_qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.parse_qs/</guid>
      <description>Name cowboy_req:parse_qs - Parse the query string
Description parse_qs(Req :: cowboy_req:req()) -&amp;gt; [{Key :: binary(), Value :: binary() | true}]  Parse the query string as a list of key/value pairs.
Arguments Req The Req object.
  Return value The parsed query string is returned as a list of key/value pairs. The key is a binary string. The value is either a binary string, or the atom true. Both key and value are case sensitive.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.parse_qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.parse_qs/</guid>
      <description>Name cowboy_req:parse_qs - Parse the query string
Description parse_qs(Req :: cowboy_req:req()) -&amp;gt; [{Key :: binary(), Value :: binary() | true}]  Parse the query string as a list of key/value pairs.
Arguments Req The Req object.
  Return value The parsed query string is returned as a list of key/value pairs. The key is a binary string. The value is either a binary string, or the atom true. Both key and value are case sensitive.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.parse_qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.parse_qs/</guid>
      <description>Name cowboy_req:parse_qs - Parse the query string
Description parse_qs(Req :: cowboy_req:req()) -&amp;gt; [{Key :: binary(), Value :: binary() | true}]  Parse the query string as a list of key/value pairs.
Arguments Req The Req object.
  Return value The parsed query string is returned as a list of key/value pairs. The key is a binary string. The value is either a binary string, or the atom true. Both key and value are case sensitive.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.parse_qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.parse_qs/</guid>
      <description>Name cowboy_req:parse_qs - Parse the query string
Description parse_qs(Req :: cowboy_req:req()) -&amp;gt; [{Key :: binary(), Value :: binary() | true}]  Parse the query string as a list of key/value pairs.
Arguments Req The Req object.
  Return value The parsed query string is returned as a list of key/value pairs. The key is a binary string. The value is either a binary string, or the atom true. Both key and value are case sensitive.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.parse_qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.parse_qs/</guid>
      <description>Name cowboy_req:parse_qs - Parse the query string
Description parse_qs(Req :: cowboy_req:req()) -&amp;gt; [{Key :: binary(), Value :: binary() | true}]  Parse the query string as a list of key/value pairs.
Arguments Req The Req object.
  Return value The parsed query string is returned as a list of key/value pairs. The key is a binary string. The value is either a binary string, or the atom true. Both key and value are case sensitive.</description>
    </item>
    
    <item>
      <title>cowboy_req:parse_qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.parse_qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.parse_qs/</guid>
      <description>Name cowboy_req:parse_qs - Parse the query string
Description parse_qs(Req :: cowboy_req:req()) -&amp;gt; [{Key :: binary(), Value :: binary() | true}]  Parse the query string as a list of key/value pairs.
Arguments Req The Req object.
  Return value The parsed query string is returned as a list of key/value pairs. The key is a binary string. The value is either a binary string, or the atom true. Both key and value are case sensitive.</description>
    </item>
    
    <item>
      <title>cowboy_req:path(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.path/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.path/</guid>
      <description>Name cowboy_req:path - URI path
Description path(Req :: cowboy_req:req()) -&amp;gt; Path :: binary()  Return the path of the effective request URI.
The path can also be obtained using pattern matching:
#{path := Path} = Req.  Arguments Req The Req object.
  Return value The path is returned as a binary string. It is case sensitive.
Changelog 2.0: Only the path is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:path(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.path/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.path/</guid>
      <description>Name cowboy_req:path - URI path
Description path(Req :: cowboy_req:req()) -&amp;gt; Path :: binary()  Return the path of the effective request URI.
The path can also be obtained using pattern matching:
#{path := Path} = Req.  Arguments Req The Req object.
  Return value The path is returned as a binary string. It is case sensitive.
Changelog 2.0: Only the path is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:path(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.path/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.path/</guid>
      <description>Name cowboy_req:path - URI path
Description path(Req :: cowboy_req:req()) -&amp;gt; Path :: binary()  Return the path of the effective request URI.
The path can also be obtained using pattern matching:
#{path := Path} = Req.  Arguments Req The Req object.
  Return value The path is returned as a binary string. It is case sensitive.
Changelog 2.0: Only the path is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:path(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.path/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.path/</guid>
      <description>Name cowboy_req:path - URI path
Description path(Req :: cowboy_req:req()) -&amp;gt; Path :: binary()  Return the path of the effective request URI.
The path can also be obtained using pattern matching:
#{path := Path} = Req.  Arguments Req The Req object.
  Return value The path is returned as a binary string. It is case sensitive.
Changelog 2.0: Only the path is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:path(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.path/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.path/</guid>
      <description>Name cowboy_req:path - URI path
Description path(Req :: cowboy_req:req()) -&amp;gt; Path :: binary()  Return the path of the effective request URI.
The path can also be obtained using pattern matching:
#{path := Path} = Req.  Arguments Req The Req object.
  Return value The path is returned as a binary string. It is case sensitive.
Changelog 2.0: Only the path is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:path(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.path/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.path/</guid>
      <description>Name cowboy_req:path - URI path
Description path(Req :: cowboy_req:req()) -&amp;gt; Path :: binary()  Return the path of the effective request URI.
The path can also be obtained using pattern matching:
#{path := Path} = Req.  Arguments Req The Req object.
  Return value The path is returned as a binary string. It is case sensitive.
Changelog 2.0: Only the path is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:path_info(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.path_info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.path_info/</guid>
      <description>Name cowboy_req:path_info - Access the route&amp;apos;s trailing path segments
Description path_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the trailing path segments.
This is the part of the host name that was matched using the ... notation.
Arguments Req The Req object.
  Return value The tokens are returned as a list of case sensitive binary strings.
Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:path_info(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.path_info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.path_info/</guid>
      <description>Name cowboy_req:path_info - Access the route&amp;apos;s trailing path segments
Description path_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the trailing path segments.
This is the part of the host name that was matched using the ... notation.
Arguments Req The Req object.
  Return value The tokens are returned as a list of case sensitive binary strings.
Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:path_info(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.path_info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.path_info/</guid>
      <description>Name cowboy_req:path_info - Access the route&amp;apos;s trailing path segments
Description path_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the trailing path segments.
This is the part of the host name that was matched using the ... notation.
Arguments Req The Req object.
  Return value The tokens are returned as a list of case sensitive binary strings.
Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:path_info(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.path_info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.path_info/</guid>
      <description>Name cowboy_req:path_info - Access the route&amp;apos;s trailing path segments
Description path_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the trailing path segments.
This is the part of the host name that was matched using the ... notation.
Arguments Req The Req object.
  Return value The tokens are returned as a list of case sensitive binary strings.
Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:path_info(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.path_info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.path_info/</guid>
      <description>Name cowboy_req:path_info - Access the route&amp;apos;s trailing path segments
Description path_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the trailing path segments.
This is the part of the host name that was matched using the ... notation.
Arguments Req The Req object.
  Return value The tokens are returned as a list of case sensitive binary strings.
Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:path_info(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.path_info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.path_info/</guid>
      <description>Name cowboy_req:path_info - Access the route&amp;apos;s trailing path segments
Description path_info(Req :: cowboy_req:req()) -&amp;gt; cowboy_router:tokens()  Return the tokens for the trailing path segments.
This is the part of the host name that was matched using the ... notation.
Arguments Req The Req object.
  Return value The tokens are returned as a list of case sensitive binary strings.
Changelog 2.0: Only the tokens are returned, they are no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:peer(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.peer/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.peer/</guid>
      <description>Name cowboy_req:peer - Peer address and port
Description peer(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the peer&amp;apos;s IP address and port number.
The peer information can also be obtained using pattern matching:
#{peer := {IP, Port}} = Req.  Arguments Req The Req object.
  Return value The peer&amp;apos;s IP address and port number.
The peer is not necessarily the client&amp;apos;s IP address and port. It is the IP address of the endpoint connecting directly to the server, which may be a gateway or a proxy.</description>
    </item>
    
    <item>
      <title>cowboy_req:peer(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.peer/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.peer/</guid>
      <description>Name cowboy_req:peer - Peer address and port
Description peer(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the peer&amp;apos;s IP address and port number.
The peer information can also be obtained using pattern matching:
#{peer := {IP, Port}} = Req.  Arguments Req The Req object.
  Return value The peer&amp;apos;s IP address and port number.
The peer is not necessarily the client&amp;apos;s IP address and port. It is the IP address of the endpoint connecting directly to the server, which may be a gateway or a proxy.</description>
    </item>
    
    <item>
      <title>cowboy_req:peer(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.peer/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.peer/</guid>
      <description>Name cowboy_req:peer - Peer address and port
Description peer(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the peer&amp;apos;s IP address and port number.
The peer information can also be obtained using pattern matching:
#{peer := {IP, Port}} = Req.  Arguments Req The Req object.
  Return value The peer&amp;apos;s IP address and port number.
The peer is not necessarily the client&amp;apos;s IP address and port. It is the IP address of the endpoint connecting directly to the server, which may be a gateway or a proxy.</description>
    </item>
    
    <item>
      <title>cowboy_req:peer(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.peer/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.peer/</guid>
      <description>Name cowboy_req:peer - Peer address and port
Description peer(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the peer&amp;apos;s IP address and port number.
The peer information can also be obtained using pattern matching:
#{peer := {IP, Port}} = Req.  Arguments Req The Req object.
  Return value The peer&amp;apos;s IP address and port number.
The peer is not necessarily the client&amp;apos;s IP address and port. It is the IP address of the endpoint connecting directly to the server, which may be a gateway or a proxy.</description>
    </item>
    
    <item>
      <title>cowboy_req:peer(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.peer/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.peer/</guid>
      <description>Name cowboy_req:peer - Peer address and port
Description peer(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the peer&amp;apos;s IP address and port number.
The peer information can also be obtained using pattern matching:
#{peer := {IP, Port}} = Req.  Arguments Req The Req object.
  Return value The peer&amp;apos;s IP address and port number.
The peer is not necessarily the client&amp;apos;s IP address and port. It is the IP address of the endpoint connecting directly to the server, which may be a gateway or a proxy.</description>
    </item>
    
    <item>
      <title>cowboy_req:peer(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.peer/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.peer/</guid>
      <description>Name cowboy_req:peer - Peer address and port
Description peer(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the peer&amp;apos;s IP address and port number.
The peer information can also be obtained using pattern matching:
#{peer := {IP, Port}} = Req.  Arguments Req The Req object.
  Return value The peer&amp;apos;s IP address and port number.
The peer is not necessarily the client&amp;apos;s IP address and port. It is the IP address of the endpoint connecting directly to the server, which may be a gateway or a proxy.</description>
    </item>
    
    <item>
      <title>cowboy_req:port(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.port/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.port/</guid>
      <description>Name cowboy_req:port - URI port number
Description port(Req :: cowboy_req:req()) -&amp;gt; Port :: inet:port_number()  Return the port number of the effective request URI.
Note that the port number returned by this function is obtained by parsing the host header. It may be different from the port the peer used to connect to Cowboy.
The port number can also be obtained using pattern matching:
#{port := Port} = Req.  Arguments Req The Req object.</description>
    </item>
    
    <item>
      <title>cowboy_req:port(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.port/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.port/</guid>
      <description>Name cowboy_req:port - URI port number
Description port(Req :: cowboy_req:req()) -&amp;gt; Port :: inet:port_number()  Return the port number of the effective request URI.
Note that the port number returned by this function is obtained by parsing the host header. It may be different from the port the peer used to connect to Cowboy.
The port number can also be obtained using pattern matching:
#{port := Port} = Req.  Arguments Req The Req object.</description>
    </item>
    
    <item>
      <title>cowboy_req:port(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.port/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.port/</guid>
      <description>Name cowboy_req:port - URI port number
Description port(Req :: cowboy_req:req()) -&amp;gt; Port :: inet:port_number()  Return the port number of the effective request URI.
Note that the port number returned by this function is obtained by parsing the host header. It may be different from the port the peer used to connect to Cowboy.
The port number can also be obtained using pattern matching:
#{port := Port} = Req.  Arguments Req The Req object.</description>
    </item>
    
    <item>
      <title>cowboy_req:port(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.port/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.port/</guid>
      <description>Name cowboy_req:port - URI port number
Description port(Req :: cowboy_req:req()) -&amp;gt; Port :: inet:port_number()  Return the port number of the effective request URI.
Note that the port number returned by this function is obtained by parsing the host header. It may be different from the port the peer used to connect to Cowboy.
The port number can also be obtained using pattern matching:
#{port := Port} = Req.  Arguments Req The Req object.</description>
    </item>
    
    <item>
      <title>cowboy_req:port(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.port/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.port/</guid>
      <description>Name cowboy_req:port - URI port number
Description port(Req :: cowboy_req:req()) -&amp;gt; Port :: inet:port_number()  Return the port number of the effective request URI.
Note that the port number returned by this function is obtained by parsing the host header. It may be different from the port the peer used to connect to Cowboy.
The port number can also be obtained using pattern matching:
#{port := Port} = Req.  Arguments Req The Req object.</description>
    </item>
    
    <item>
      <title>cowboy_req:port(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.port/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.port/</guid>
      <description>Name cowboy_req:port - URI port number
Description port(Req :: cowboy_req:req()) -&amp;gt; Port :: inet:port_number()  Return the port number of the effective request URI.
Note that the port number returned by this function is obtained by parsing the host header. It may be different from the port the peer used to connect to Cowboy.
The port number can also be obtained using pattern matching:
#{port := Port} = Req.  Arguments Req The Req object.</description>
    </item>
    
    <item>
      <title>cowboy_req:push(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.push/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.push/</guid>
      <description>Name cowboy_req:push - Push a resource to the client
Description push(Path, Headers, Req :: cowboy_req:req()) -&amp;gt; push(Path, Headers, Req, #{}) push(Path, Headers, Req :: cowboy_req:req(), Opts) -&amp;gt; ok Path :: iodata() %% case sensitive Headers :: cowboy:http_headers() Opts :: cowboy_req:push_opts()  Push a resource to the client.
Cowboy handles push requests the same way as if they came from the client, including the creation of a request handling process, routing and middlewares and so on.</description>
    </item>
    
    <item>
      <title>cowboy_req:push(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.push/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.push/</guid>
      <description>Name cowboy_req:push - Push a resource to the client
Description push(Path, Headers, Req :: cowboy_req:req()) -&amp;gt; push(Path, Headers, Req, #{}) push(Path, Headers, Req :: cowboy_req:req(), Opts) -&amp;gt; ok Path :: iodata() %% case sensitive Headers :: cowboy:http_headers() Opts :: cowboy_req:push_opts()  Push a resource to the client.
Cowboy handles push requests the same way as if they came from the client, including the creation of a request handling process, routing and middlewares and so on.</description>
    </item>
    
    <item>
      <title>cowboy_req:push(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.push/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.push/</guid>
      <description>Name cowboy_req:push - Push a resource to the client
Description push(Path, Headers, Req :: cowboy_req:req()) -&amp;gt; push(Path, Headers, Req, #{}) push(Path, Headers, Req :: cowboy_req:req(), Opts) -&amp;gt; ok Path :: iodata() %% case sensitive Headers :: cowboy:http_headers() Opts :: cowboy_req:push_opts()  Push a resource to the client.
Cowboy handles push requests the same way as if they came from the client, including the creation of a request handling process, routing and middlewares and so on.</description>
    </item>
    
    <item>
      <title>cowboy_req:push(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.push/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.push/</guid>
      <description>Name cowboy_req:push - Push a resource to the client
Description push(Path, Headers, Req :: cowboy_req:req()) -&amp;gt; push(Path, Headers, Req, #{}) push(Path, Headers, Req :: cowboy_req:req(), Opts) -&amp;gt; ok Path :: iodata() %% case sensitive Headers :: cowboy:http_headers() Opts :: cowboy_req:push_opts()  Push a resource to the client.
Cowboy handles push requests the same way as if they came from the client, including the creation of a request handling process, routing and middlewares and so on.</description>
    </item>
    
    <item>
      <title>cowboy_req:push(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.push/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.push/</guid>
      <description>Name cowboy_req:push - Push a resource to the client
Description push(Path, Headers, Req :: cowboy_req:req()) -&amp;gt; push(Path, Headers, Req, #{}) push(Path, Headers, Req :: cowboy_req:req(), Opts) -&amp;gt; ok Path :: iodata() %% case sensitive Headers :: cowboy:http_headers() Opts :: cowboy_req:push_opts()  Push a resource to the client.
Cowboy handles push requests the same way as if they came from the client, including the creation of a request handling process, routing and middlewares and so on.</description>
    </item>
    
    <item>
      <title>cowboy_req:push(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.push/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.push/</guid>
      <description>Name cowboy_req:push - Push a resource to the client
Description push(Path, Headers, Req :: cowboy_req:req()) -&amp;gt; push(Path, Headers, Req, #{}) push(Path, Headers, Req :: cowboy_req:req(), Opts) -&amp;gt; ok Path :: iodata() %% case sensitive Headers :: cowboy:http_headers() Opts :: cowboy_req:push_opts()  Push a resource to the client.
Cowboy handles push requests the same way as if they came from the client, including the creation of a request handling process, routing and middlewares and so on.</description>
    </item>
    
    <item>
      <title>cowboy_req:qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.qs/</guid>
      <description>Name cowboy_req:qs - URI query string
Description qs(Req :: cowboy_req:req()) -&amp;gt; Qs :: binary()  Return the query string of the effective request URI.
The query string can also be obtained using pattern matching:
#{qs := Qs} = Req.  Arguments Req The Req object.
  Return value The query string is returned as a binary string. It is case sensitive.
Changelog 2.0: Only the query string is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.qs/</guid>
      <description>Name cowboy_req:qs - URI query string
Description qs(Req :: cowboy_req:req()) -&amp;gt; Qs :: binary()  Return the query string of the effective request URI.
The query string can also be obtained using pattern matching:
#{qs := Qs} = Req.  Arguments Req The Req object.
  Return value The query string is returned as a binary string. It is case sensitive.
Changelog 2.0: Only the query string is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.qs/</guid>
      <description>Name cowboy_req:qs - URI query string
Description qs(Req :: cowboy_req:req()) -&amp;gt; Qs :: binary()  Return the query string of the effective request URI.
The query string can also be obtained using pattern matching:
#{qs := Qs} = Req.  Arguments Req The Req object.
  Return value The query string is returned as a binary string. It is case sensitive.
Changelog 2.0: Only the query string is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.qs/</guid>
      <description>Name cowboy_req:qs - URI query string
Description qs(Req :: cowboy_req:req()) -&amp;gt; Qs :: binary()  Return the query string of the effective request URI.
The query string can also be obtained using pattern matching:
#{qs := Qs} = Req.  Arguments Req The Req object.
  Return value The query string is returned as a binary string. It is case sensitive.
Changelog 2.0: Only the query string is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.qs/</guid>
      <description>Name cowboy_req:qs - URI query string
Description qs(Req :: cowboy_req:req()) -&amp;gt; Qs :: binary()  Return the query string of the effective request URI.
The query string can also be obtained using pattern matching:
#{qs := Qs} = Req.  Arguments Req The Req object.
  Return value The query string is returned as a binary string. It is case sensitive.
Changelog 2.0: Only the query string is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:qs(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.qs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.qs/</guid>
      <description>Name cowboy_req:qs - URI query string
Description qs(Req :: cowboy_req:req()) -&amp;gt; Qs :: binary()  Return the query string of the effective request URI.
The query string can also be obtained using pattern matching:
#{qs := Qs} = Req.  Arguments Req The Req object.
  Return value The query string is returned as a binary string. It is case sensitive.
Changelog 2.0: Only the query string is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_and_match_urlencoded_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.read_and_match_urlencoded_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.read_and_match_urlencoded_body/</guid>
      <description>Name cowboy_req:read_and_match_urlencoded_body - Read, parse and match a urlencoded request body against constraints
Description read_and_match_urlencoded_body(Fields, Req) -&amp;gt; read_and_match_urlencoded_body(Fields, Req, #{}) read_and_match_urlencoded_body(Fields, Req, Opts) -&amp;gt; {ok, Body, Req} Fields :: cowboy:fields() Req :: cowboy_req:req() Opts :: cowboy_req:read_body_opts() Body :: #{atom() =&amp;gt; any()}  Read, parse and match a urlencoded request body against constraints.
This function reads the request body and parses it as application/x-www-form-urlencoded. It then applies the given field constraints to the urlencoded data and returns the result as a map.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_and_match_urlencoded_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_and_match_urlencoded_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_and_match_urlencoded_body/</guid>
      <description>Name cowboy_req:read_and_match_urlencoded_body - Read, parse and match a urlencoded request body against constraints
Description read_and_match_urlencoded_body(Fields, Req) -&amp;gt; read_and_match_urlencoded_body(Fields, Req, #{}) read_and_match_urlencoded_body(Fields, Req, Opts) -&amp;gt; {ok, Body, Req} Fields :: cowboy:fields() Req :: cowboy_req:req() Opts :: cowboy_req:read_body_opts() Body :: #{atom() =&amp;gt; any()}  Read, parse and match a urlencoded request body against constraints.
This function reads the request body and parses it as application/x-www-form-urlencoded. It then applies the given field constraints to the urlencoded data and returns the result as a map.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_and_match_urlencoded_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.read_and_match_urlencoded_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.read_and_match_urlencoded_body/</guid>
      <description>Name cowboy_req:read_and_match_urlencoded_body - Read, parse and match a urlencoded request body against constraints
Description read_and_match_urlencoded_body(Fields, Req) -&amp;gt; read_and_match_urlencoded_body(Fields, Req, #{}) read_and_match_urlencoded_body(Fields, Req, Opts) -&amp;gt; {ok, Body, Req} Fields :: cowboy:fields() Req :: cowboy_req:req() Opts :: cowboy_req:read_body_opts() Body :: #{atom() =&amp;gt; any()}  Read, parse and match a urlencoded request body against constraints.
This function reads the request body and parses it as application/x-www-form-urlencoded. It then applies the given field constraints to the urlencoded data and returns the result as a map.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.read_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.read_body/</guid>
      <description>Name cowboy_req:read_body - Read the request body
Description read_body(Req :: cowboy_req:req()) -&amp;gt; read_body(Req, #{}) read_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the request body.
This function reads a chunk of the request body. A more tuple is returned when more data remains to be read. Call the function repeatedly until an ok tuple is returned to read the entire body.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.read_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.read_body/</guid>
      <description>Name cowboy_req:read_body - Read the request body
Description read_body(Req :: cowboy_req:req()) -&amp;gt; read_body(Req, #{}) read_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the request body.
This function reads a chunk of the request body. A more tuple is returned when more data remains to be read. Call the function repeatedly until an ok tuple is returned to read the entire body.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.read_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.read_body/</guid>
      <description>Name cowboy_req:read_body - Read the request body
Description read_body(Req :: cowboy_req:req()) -&amp;gt; read_body(Req, #{}) read_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the request body.
This function reads a chunk of the request body. A more tuple is returned when more data remains to be read. Call the function repeatedly until an ok tuple is returned to read the entire body.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.read_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.read_body/</guid>
      <description>Name cowboy_req:read_body - Read the request body
Description read_body(Req :: cowboy_req:req()) -&amp;gt; read_body(Req, #{}) read_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the request body.
This function reads a chunk of the request body. A more tuple is returned when more data remains to be read. Call the function repeatedly until an ok tuple is returned to read the entire body.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_body/</guid>
      <description>Name cowboy_req:read_body - Read the request body
Description read_body(Req :: cowboy_req:req()) -&amp;gt; read_body(Req, #{}) read_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the request body.
This function reads a chunk of the request body. A more tuple is returned when more data remains to be read. Call the function repeatedly until an ok tuple is returned to read the entire body.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.read_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.read_body/</guid>
      <description>Name cowboy_req:read_body - Read the request body
Description read_body(Req :: cowboy_req:req()) -&amp;gt; read_body(Req, #{}) read_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the request body.
This function reads a chunk of the request body. A more tuple is returned when more data remains to be read. Call the function repeatedly until an ok tuple is returned to read the entire body.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_part(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.read_part/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.read_part/</guid>
      <description>Name cowboy_req:read_part - Read the next multipart headers
Description read_part(Req :: cowboy_req:req()) -&amp;gt; read_part(Req, #{}) read_part(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Headers, Req} | {done, Req} Opts :: cowboy_req:read_body_opts() Headers :: #{binary() =&amp;gt; binary()}  Read the next part of a multipart body.
This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function parses and returns headers.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_part(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.read_part/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.read_part/</guid>
      <description>Name cowboy_req:read_part - Read the next multipart headers
Description read_part(Req :: cowboy_req:req()) -&amp;gt; read_part(Req, #{}) read_part(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Headers, Req} | {done, Req} Opts :: cowboy_req:read_body_opts() Headers :: #{binary() =&amp;gt; binary()}  Read the next part of a multipart body.
This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function parses and returns headers.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_part(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.read_part/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.read_part/</guid>
      <description>Name cowboy_req:read_part - Read the next multipart headers
Description read_part(Req :: cowboy_req:req()) -&amp;gt; read_part(Req, #{}) read_part(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Headers, Req} | {done, Req} Opts :: cowboy_req:read_body_opts() Headers :: #{binary() =&amp;gt; binary()}  Read the next part of a multipart body.
This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function parses and returns headers.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_part(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.read_part/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.read_part/</guid>
      <description>Name cowboy_req:read_part - Read the next multipart headers
Description read_part(Req :: cowboy_req:req()) -&amp;gt; read_part(Req, #{}) read_part(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Headers, Req} | {done, Req} Opts :: cowboy_req:read_body_opts() Headers :: #{binary() =&amp;gt; binary()}  Read the next part of a multipart body.
This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function parses and returns headers.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_part(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_part/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_part/</guid>
      <description>Name cowboy_req:read_part - Read the next multipart headers
Description read_part(Req :: cowboy_req:req()) -&amp;gt; read_part(Req, #{}) read_part(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Headers, Req} | {done, Req} Opts :: cowboy_req:read_body_opts() Headers :: #{binary() =&amp;gt; binary()}  Read the next part of a multipart body.
This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function parses and returns headers.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_part(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.read_part/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.read_part/</guid>
      <description>Name cowboy_req:read_part - Read the next multipart headers
Description read_part(Req :: cowboy_req:req()) -&amp;gt; read_part(Req, #{}) read_part(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Headers, Req} | {done, Req} Opts :: cowboy_req:read_body_opts() Headers :: #{binary() =&amp;gt; binary()}  Read the next part of a multipart body.
This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function parses and returns headers.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_part_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.read_part_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.read_part_body/</guid>
      <description>Name cowboy_req:read_part_body - Read the current part&amp;apos;s body
Description read_part_body(Req :: cowboy_req:req()) -&amp;gt; read_part_body(Req, #{}) read_part_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the body of the current part of the multipart message.
This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function returns the body of the current part.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_part_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.read_part_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.read_part_body/</guid>
      <description>Name cowboy_req:read_part_body - Read the current part&amp;apos;s body
Description read_part_body(Req :: cowboy_req:req()) -&amp;gt; read_part_body(Req, #{}) read_part_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the body of the current part of the multipart message.
This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function returns the body of the current part.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_part_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.read_part_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.read_part_body/</guid>
      <description>Name cowboy_req:read_part_body - Read the current part&amp;apos;s body
Description read_part_body(Req :: cowboy_req:req()) -&amp;gt; read_part_body(Req, #{}) read_part_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the body of the current part of the multipart message.
This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function returns the body of the current part.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_part_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.read_part_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.read_part_body/</guid>
      <description>Name cowboy_req:read_part_body - Read the current part&amp;apos;s body
Description read_part_body(Req :: cowboy_req:req()) -&amp;gt; read_part_body(Req, #{}) read_part_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the body of the current part of the multipart message.
This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function returns the body of the current part.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_part_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_part_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_part_body/</guid>
      <description>Name cowboy_req:read_part_body - Read the current part&amp;apos;s body
Description read_part_body(Req :: cowboy_req:req()) -&amp;gt; read_part_body(Req, #{}) read_part_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the body of the current part of the multipart message.
This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function returns the body of the current part.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_part_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.read_part_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.read_part_body/</guid>
      <description>Name cowboy_req:read_part_body - Read the current part&amp;apos;s body
Description read_part_body(Req :: cowboy_req:req()) -&amp;gt; read_part_body(Req, #{}) read_part_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Data :: binary(), Req} | {more, Data :: binary(), Req} Opts :: cowboy_req:read_body_opts()  Read the body of the current part of the multipart message.
This function reads the request body and parses it as multipart. Each parts of a multipart representation have their own headers and body. This function returns the body of the current part.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_urlencoded_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.read_urlencoded_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.read_urlencoded_body/</guid>
      <description>Name cowboy_req:read_urlencoded_body - Read and parse a urlencoded request body
Description read_urlencoded_body(Req :: cowboy_req:req()) -&amp;gt; read_urlencoded_body(Req, #{}) read_urlencoded_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Body, Req} Opts :: cowboy_req:read_body_opts() Body :: [{Key :: binary(), Value :: binary() | true}]  Read and parse a urlencoded request body.
This function reads the request body and parses it as application/x-www-form-urlencoded. It returns a list of key/values.
The urlencoded media type is used by Web browsers when submitting HTML forms using the POST method.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_urlencoded_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.read_urlencoded_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.read_urlencoded_body/</guid>
      <description>Name cowboy_req:read_urlencoded_body - Read and parse a urlencoded request body
Description read_urlencoded_body(Req :: cowboy_req:req()) -&amp;gt; read_urlencoded_body(Req, #{}) read_urlencoded_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Body, Req} Opts :: cowboy_req:read_body_opts() Body :: [{Key :: binary(), Value :: binary() | true}]  Read and parse a urlencoded request body.
This function reads the request body and parses it as application/x-www-form-urlencoded. It returns a list of key/values.
The urlencoded media type is used by Web browsers when submitting HTML forms using the POST method.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_urlencoded_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.read_urlencoded_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.read_urlencoded_body/</guid>
      <description>Name cowboy_req:read_urlencoded_body - Read and parse a urlencoded request body
Description read_urlencoded_body(Req :: cowboy_req:req()) -&amp;gt; read_urlencoded_body(Req, #{}) read_urlencoded_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Body, Req} Opts :: cowboy_req:read_body_opts() Body :: [{Key :: binary(), Value :: binary() | true}]  Read and parse a urlencoded request body.
This function reads the request body and parses it as application/x-www-form-urlencoded. It returns a list of key/values.
The urlencoded media type is used by Web browsers when submitting HTML forms using the POST method.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_urlencoded_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.read_urlencoded_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.read_urlencoded_body/</guid>
      <description>Name cowboy_req:read_urlencoded_body - Read and parse a urlencoded request body
Description read_urlencoded_body(Req :: cowboy_req:req()) -&amp;gt; read_urlencoded_body(Req, #{}) read_urlencoded_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Body, Req} Opts :: cowboy_req:read_body_opts() Body :: [{Key :: binary(), Value :: binary() | true}]  Read and parse a urlencoded request body.
This function reads the request body and parses it as application/x-www-form-urlencoded. It returns a list of key/values.
The urlencoded media type is used by Web browsers when submitting HTML forms using the POST method.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_urlencoded_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_urlencoded_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.read_urlencoded_body/</guid>
      <description>Name cowboy_req:read_urlencoded_body - Read and parse a urlencoded request body
Description read_urlencoded_body(Req :: cowboy_req:req()) -&amp;gt; read_urlencoded_body(Req, #{}) read_urlencoded_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Body, Req} Opts :: cowboy_req:read_body_opts() Body :: [{Key :: binary(), Value :: binary() | true}]  Read and parse a urlencoded request body.
This function reads the request body and parses it as application/x-www-form-urlencoded. It returns a list of key/values.
The urlencoded media type is used by Web browsers when submitting HTML forms using the POST method.</description>
    </item>
    
    <item>
      <title>cowboy_req:read_urlencoded_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.read_urlencoded_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.read_urlencoded_body/</guid>
      <description>Name cowboy_req:read_urlencoded_body - Read and parse a urlencoded request body
Description read_urlencoded_body(Req :: cowboy_req:req()) -&amp;gt; read_urlencoded_body(Req, #{}) read_urlencoded_body(Req :: cowboy_req:req(), Opts) -&amp;gt; {ok, Body, Req} Opts :: cowboy_req:read_body_opts() Body :: [{Key :: binary(), Value :: binary() | true}]  Read and parse a urlencoded request body.
This function reads the request body and parses it as application/x-www-form-urlencoded. It returns a list of key/values.
The urlencoded media type is used by Web browsers when submitting HTML forms using the POST method.</description>
    </item>
    
    <item>
      <title>cowboy_req:reply(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.reply/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.reply/</guid>
      <description>Name cowboy_req:reply - Send the response
Description reply(Status, Req :: cowboy_req:req()) -&amp;gt; reply(StatusCode, #{}, Req) reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req reply(Status, Headers, Body, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers() Body :: cowboy_req:resp_body()  Send the response.
The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
    </item>
    
    <item>
      <title>cowboy_req:reply(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.reply/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.reply/</guid>
      <description>Name cowboy_req:reply - Send the response
Description reply(Status, Req :: cowboy_req:req()) -&amp;gt; reply(StatusCode, #{}, Req) reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req reply(Status, Headers, Body, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers() Body :: cowboy_req:resp_body()  Send the response.
The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
    </item>
    
    <item>
      <title>cowboy_req:reply(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.reply/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.reply/</guid>
      <description>Name cowboy_req:reply - Send the response
Description reply(Status, Req :: cowboy_req:req()) -&amp;gt; reply(StatusCode, #{}, Req) reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req reply(Status, Headers, Body, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers() Body :: cowboy_req:resp_body()  Send the response.
The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
    </item>
    
    <item>
      <title>cowboy_req:reply(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.reply/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.reply/</guid>
      <description>Name cowboy_req:reply - Send the response
Description reply(Status, Req :: cowboy_req:req()) -&amp;gt; reply(StatusCode, #{}, Req) reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req reply(Status, Headers, Body, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers() Body :: cowboy_req:resp_body()  Send the response.
The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
    </item>
    
    <item>
      <title>cowboy_req:reply(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.reply/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.reply/</guid>
      <description>Name cowboy_req:reply - Send the response
Description reply(Status, Req :: cowboy_req:req()) -&amp;gt; reply(StatusCode, #{}, Req) reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req reply(Status, Headers, Body, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers() Body :: cowboy_req:resp_body()  Send the response.
The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
    </item>
    
    <item>
      <title>cowboy_req:reply(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.reply/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.reply/</guid>
      <description>Name cowboy_req:reply - Send the response
Description reply(Status, Req :: cowboy_req:req()) -&amp;gt; reply(StatusCode, #{}, Req) reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req reply(Status, Headers, Body, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers() Body :: cowboy_req:resp_body()  Send the response.
The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
    </item>
    
    <item>
      <title>cowboy_req:resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.resp_header/</guid>
      <description>Name cowboy_req:resp_header - Response header
Description resp_header(Name, Req) -&amp;gt; resp_header(Name, Req, undefined) resp_header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given response header.
The response header must have been set previously using cowboy_req:set_resp_header(3) or cowboy_req:set_resp_headers(3).
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
    </item>
    
    <item>
      <title>cowboy_req:resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.resp_header/</guid>
      <description>Name cowboy_req:resp_header - Response header
Description resp_header(Name, Req) -&amp;gt; resp_header(Name, Req, undefined) resp_header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given response header.
The response header must have been set previously using cowboy_req:set_resp_header(3) or cowboy_req:set_resp_headers(3).
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
    </item>
    
    <item>
      <title>cowboy_req:resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.resp_header/</guid>
      <description>Name cowboy_req:resp_header - Response header
Description resp_header(Name, Req) -&amp;gt; resp_header(Name, Req, undefined) resp_header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given response header.
The response header must have been set previously using cowboy_req:set_resp_header(3) or cowboy_req:set_resp_headers(3).
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
    </item>
    
    <item>
      <title>cowboy_req:resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.resp_header/</guid>
      <description>Name cowboy_req:resp_header - Response header
Description resp_header(Name, Req) -&amp;gt; resp_header(Name, Req, undefined) resp_header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given response header.
The response header must have been set previously using cowboy_req:set_resp_header(3) or cowboy_req:set_resp_headers(3).
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
    </item>
    
    <item>
      <title>cowboy_req:resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.resp_header/</guid>
      <description>Name cowboy_req:resp_header - Response header
Description resp_header(Name, Req) -&amp;gt; resp_header(Name, Req, undefined) resp_header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given response header.
The response header must have been set previously using cowboy_req:set_resp_header(3) or cowboy_req:set_resp_headers(3).
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
    </item>
    
    <item>
      <title>cowboy_req:resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.resp_header/</guid>
      <description>Name cowboy_req:resp_header - Response header
Description resp_header(Name, Req) -&amp;gt; resp_header(Name, Req, undefined) resp_header(Name, Req, Default) -&amp;gt; binary() | Default Name :: binary() %% lowercase; case insensitive Req :: cowboy_req:req() Default :: any()  Return the value for the given response header.
The response header must have been set previously using cowboy_req:set_resp_header(3) or cowboy_req:set_resp_headers(3).
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.</description>
    </item>
    
    <item>
      <title>cowboy_req:resp_headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.resp_headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.resp_headers/</guid>
      <description>Name cowboy_req:resp_headers - Response headers
Description resp_headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all response headers.
Arguments Req The Req object.
  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
Changelog 2.0: Function introduced.   Examples Get all response headers Headers = cowboy_req:resp_headers(Req).  See also cowboy_req(3), cowboy_req:resp_header(3), cowboy_req:set_resp_header(3), cowboy_req:set_resp_headers(3)</description>
    </item>
    
    <item>
      <title>cowboy_req:resp_headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.resp_headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.resp_headers/</guid>
      <description>Name cowboy_req:resp_headers - Response headers
Description resp_headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all response headers.
Arguments Req The Req object.
  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
Changelog 2.0: Function introduced.   Examples Get all response headers Headers = cowboy_req:resp_headers(Req).  See also cowboy_req(3), cowboy_req:resp_header(3), cowboy_req:set_resp_header(3), cowboy_req:set_resp_headers(3)</description>
    </item>
    
    <item>
      <title>cowboy_req:resp_headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.resp_headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.resp_headers/</guid>
      <description>Name cowboy_req:resp_headers - Response headers
Description resp_headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all response headers.
Arguments Req The Req object.
  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
Changelog 2.0: Function introduced.   Examples Get all response headers Headers = cowboy_req:resp_headers(Req).  See also cowboy_req(3), cowboy_req:resp_header(3), cowboy_req:set_resp_header(3), cowboy_req:set_resp_headers(3)</description>
    </item>
    
    <item>
      <title>cowboy_req:resp_headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.resp_headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.resp_headers/</guid>
      <description>Name cowboy_req:resp_headers - Response headers
Description resp_headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all response headers.
Arguments Req The Req object.
  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
Changelog 2.0: Function introduced.   Examples Get all response headers Headers = cowboy_req:resp_headers(Req).  See also cowboy_req(3), cowboy_req:resp_header(3), cowboy_req:set_resp_header(3), cowboy_req:set_resp_headers(3)</description>
    </item>
    
    <item>
      <title>cowboy_req:resp_headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.resp_headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.resp_headers/</guid>
      <description>Name cowboy_req:resp_headers - Response headers
Description resp_headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all response headers.
Arguments Req The Req object.
  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
Changelog 2.0: Function introduced.   Examples Get all response headers Headers = cowboy_req:resp_headers(Req).  See also cowboy_req(3), cowboy_req:resp_header(3), cowboy_req:set_resp_header(3), cowboy_req:set_resp_headers(3)</description>
    </item>
    
    <item>
      <title>cowboy_req:resp_headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.resp_headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.resp_headers/</guid>
      <description>Name cowboy_req:resp_headers - Response headers
Description resp_headers(Req :: cowboy_req:req()) -&amp;gt; cowboy:http_headers()  Return all response headers.
Arguments Req The Req object.
  Return value Headers are returned as a map with keys being lowercase binary strings, and values as binary strings.
Changelog 2.0: Function introduced.   Examples Get all response headers Headers = cowboy_req:resp_headers(Req).  See also cowboy_req(3), cowboy_req:resp_header(3), cowboy_req:set_resp_header(3), cowboy_req:set_resp_headers(3)</description>
    </item>
    
    <item>
      <title>cowboy_req:scheme(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.scheme/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.scheme/</guid>
      <description>Name cowboy_req:scheme - URI scheme
Description scheme(Req :: cowboy_req:req()) -&amp;gt; Scheme :: binary()  Return the scheme of the effective request URI.
The scheme can also be obtained using pattern matching:
#{scheme := Scheme} = Req.  Arguments Req The Req object.
  Return value The scheme is returned as a binary. It is case insensitive.
Cowboy will only set the scheme to &amp;lt;&amp;lt;&amp;quot;http&amp;quot;&amp;gt;&amp;gt; or &amp;lt;&amp;lt;&amp;quot;https&amp;quot;&amp;gt;&amp;gt;.
Changelog 2.0: Function introduced.</description>
    </item>
    
    <item>
      <title>cowboy_req:scheme(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.scheme/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.scheme/</guid>
      <description>Name cowboy_req:scheme - URI scheme
Description scheme(Req :: cowboy_req:req()) -&amp;gt; Scheme :: binary()  Return the scheme of the effective request URI.
The scheme can also be obtained using pattern matching:
#{scheme := Scheme} = Req.  Arguments Req The Req object.
  Return value The scheme is returned as a binary. It is case insensitive.
Cowboy will only set the scheme to &amp;lt;&amp;lt;&amp;quot;http&amp;quot;&amp;gt;&amp;gt; or &amp;lt;&amp;lt;&amp;quot;https&amp;quot;&amp;gt;&amp;gt;.
Changelog 2.0: Function introduced.</description>
    </item>
    
    <item>
      <title>cowboy_req:scheme(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.scheme/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.scheme/</guid>
      <description>Name cowboy_req:scheme - URI scheme
Description scheme(Req :: cowboy_req:req()) -&amp;gt; Scheme :: binary()  Return the scheme of the effective request URI.
The scheme can also be obtained using pattern matching:
#{scheme := Scheme} = Req.  Arguments Req The Req object.
  Return value The scheme is returned as a binary. It is case insensitive.
Cowboy will only set the scheme to &amp;lt;&amp;lt;&amp;quot;http&amp;quot;&amp;gt;&amp;gt; or &amp;lt;&amp;lt;&amp;quot;https&amp;quot;&amp;gt;&amp;gt;.
Changelog 2.0: Function introduced.</description>
    </item>
    
    <item>
      <title>cowboy_req:scheme(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.scheme/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.scheme/</guid>
      <description>Name cowboy_req:scheme - URI scheme
Description scheme(Req :: cowboy_req:req()) -&amp;gt; Scheme :: binary()  Return the scheme of the effective request URI.
The scheme can also be obtained using pattern matching:
#{scheme := Scheme} = Req.  Arguments Req The Req object.
  Return value The scheme is returned as a binary. It is case insensitive.
Cowboy will only set the scheme to &amp;lt;&amp;lt;&amp;quot;http&amp;quot;&amp;gt;&amp;gt; or &amp;lt;&amp;lt;&amp;quot;https&amp;quot;&amp;gt;&amp;gt;.
Changelog 2.0: Function introduced.</description>
    </item>
    
    <item>
      <title>cowboy_req:scheme(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.scheme/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.scheme/</guid>
      <description>Name cowboy_req:scheme - URI scheme
Description scheme(Req :: cowboy_req:req()) -&amp;gt; Scheme :: binary()  Return the scheme of the effective request URI.
The scheme can also be obtained using pattern matching:
#{scheme := Scheme} = Req.  Arguments Req The Req object.
  Return value The scheme is returned as a binary. It is case insensitive.
Cowboy will only set the scheme to &amp;lt;&amp;lt;&amp;quot;http&amp;quot;&amp;gt;&amp;gt; or &amp;lt;&amp;lt;&amp;quot;https&amp;quot;&amp;gt;&amp;gt;.
Changelog 2.0: Function introduced.</description>
    </item>
    
    <item>
      <title>cowboy_req:scheme(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.scheme/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.scheme/</guid>
      <description>Name cowboy_req:scheme - URI scheme
Description scheme(Req :: cowboy_req:req()) -&amp;gt; Scheme :: binary()  Return the scheme of the effective request URI.
The scheme can also be obtained using pattern matching:
#{scheme := Scheme} = Req.  Arguments Req The Req object.
  Return value The scheme is returned as a binary. It is case insensitive.
Cowboy will only set the scheme to &amp;lt;&amp;lt;&amp;quot;http&amp;quot;&amp;gt;&amp;gt; or &amp;lt;&amp;lt;&amp;quot;https&amp;quot;&amp;gt;&amp;gt;.
Changelog 2.0: Function introduced.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.set_resp_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.set_resp_body/</guid>
      <description>Name cowboy_req:set_resp_body - Set the response body
Description set_resp_body(Body, Req :: cowboy_req:req()) -&amp;gt; Req Body :: cowboy_req:resp_body()  Set the response body.
The response body will be sent when a reply is initiated. Note that the functions stream_reply/2,3 and reply/4 will override the body set by this function.
This function can also be used to remove a response body that was set previously. To do so, simply call this function with an empty body.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.set_resp_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.set_resp_body/</guid>
      <description>Name cowboy_req:set_resp_body - Set the response body
Description set_resp_body(Body, Req :: cowboy_req:req()) -&amp;gt; Req Body :: cowboy_req:resp_body()  Set the response body.
The response body will be sent when a reply is initiated. Note that the functions stream_reply/2,3 and reply/4 will override the body set by this function.
This function can also be used to remove a response body that was set previously. To do so, simply call this function with an empty body.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.set_resp_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.set_resp_body/</guid>
      <description>Name cowboy_req:set_resp_body - Set the response body
Description set_resp_body(Body, Req :: cowboy_req:req()) -&amp;gt; Req Body :: cowboy_req:resp_body()  Set the response body.
The response body will be sent when a reply is initiated. Note that the functions stream_reply/2,3 and reply/4 will override the body set by this function.
This function can also be used to remove a response body that was set previously. To do so, simply call this function with an empty body.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.set_resp_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.set_resp_body/</guid>
      <description>Name cowboy_req:set_resp_body - Set the response body
Description set_resp_body(Body, Req :: cowboy_req:req()) -&amp;gt; Req Body :: cowboy_req:resp_body()  Set the response body.
The response body will be sent when a reply is initiated. Note that the functions stream_reply/2,3 and reply/4 will override the body set by this function.
This function can also be used to remove a response body that was set previously. To do so, simply call this function with an empty body.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_body/</guid>
      <description>Name cowboy_req:set_resp_body - Set the response body
Description set_resp_body(Body, Req :: cowboy_req:req()) -&amp;gt; Req Body :: cowboy_req:resp_body()  Set the response body.
The response body will be sent when a reply is initiated. Note that the functions stream_reply/2,3 and reply/4 will override the body set by this function.
This function can also be used to remove a response body that was set previously. To do so, simply call this function with an empty body.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.set_resp_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.set_resp_body/</guid>
      <description>Name cowboy_req:set_resp_body - Set the response body
Description set_resp_body(Body, Req :: cowboy_req:req()) -&amp;gt; Req Body :: cowboy_req:resp_body()  Set the response body.
The response body will be sent when a reply is initiated. Note that the functions stream_reply/2,3 and reply/4 will override the body set by this function.
This function can also be used to remove a response body that was set previously. To do so, simply call this function with an empty body.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_cookie(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.set_resp_cookie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.set_resp_cookie/</guid>
      <description>Name cowboy_req:set_resp_cookie - Set a cookie
Description set_resp_cookie(Name, Value, Req :: cowboy_req:req()) -&amp;gt; set_resp_cookie(Name, Value, [], Req) set_resp_cookie(Name, Value, Req :: cowboy_req:req(), Opts) -&amp;gt; Req Name :: binary() %% case sensitive Value :: iodata() %% case sensitive Opts :: cow_cookie:cookie_opts()  Set a cookie to be sent with the response.
Note that cookie names are case sensitive.
Arguments Name Cookie name.
 Value Cookie value.
 Req The Req object.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_cookie(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.set_resp_cookie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.set_resp_cookie/</guid>
      <description>Name cowboy_req:set_resp_cookie - Set a cookie
Description set_resp_cookie(Name, Value, Req :: cowboy_req:req()) -&amp;gt; set_resp_cookie(Name, Value, [], Req) set_resp_cookie(Name, Value, Req :: cowboy_req:req(), Opts) -&amp;gt; Req Name :: binary() %% case sensitive Value :: iodata() %% case sensitive Opts :: cow_cookie:cookie_opts()  Set a cookie to be sent with the response.
Note that cookie names are case sensitive.
Arguments Name Cookie name.
 Value Cookie value.
 Req The Req object.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_cookie(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.set_resp_cookie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.set_resp_cookie/</guid>
      <description>Name cowboy_req:set_resp_cookie - Set a cookie
Description set_resp_cookie(Name, Value, Req :: cowboy_req:req()) -&amp;gt; set_resp_cookie(Name, Value, [], Req) set_resp_cookie(Name, Value, Req :: cowboy_req:req(), Opts) -&amp;gt; Req Name :: binary() %% case sensitive Value :: iodata() %% case sensitive Opts :: cow_cookie:cookie_opts()  Set a cookie to be sent with the response.
Note that cookie names are case sensitive.
Arguments Name Cookie name.
 Value Cookie value.
 Req The Req object.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_cookie(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.set_resp_cookie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.set_resp_cookie/</guid>
      <description>Name cowboy_req:set_resp_cookie - Set a cookie
Description set_resp_cookie(Name, Value, Req :: cowboy_req:req()) -&amp;gt; set_resp_cookie(Name, Value, [], Req) set_resp_cookie(Name, Value, Req :: cowboy_req:req(), Opts) -&amp;gt; Req Name :: binary() %% case sensitive Value :: iodata() %% case sensitive Opts :: cow_cookie:cookie_opts()  Set a cookie to be sent with the response.
Note that cookie names are case sensitive.
Arguments Name Cookie name.
 Value Cookie value.
 Req The Req object.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_cookie(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_cookie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_cookie/</guid>
      <description>Name cowboy_req:set_resp_cookie - Set a cookie
Description set_resp_cookie(Name, Value, Req :: cowboy_req:req()) -&amp;gt; set_resp_cookie(Name, Value, Req, #{}) set_resp_cookie(Name, Value, Req :: cowboy_req:req(), Opts) -&amp;gt; Req Name :: binary() %% case sensitive Value :: iodata() %% case sensitive Opts :: cow_cookie:cookie_opts()  Set a cookie to be sent with the response.
Note that cookie names are case sensitive.
Arguments Name Cookie name.
 Value Cookie value.
 Req The Req object.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_cookie(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.set_resp_cookie/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.set_resp_cookie/</guid>
      <description>Name cowboy_req:set_resp_cookie - Set a cookie
Description set_resp_cookie(Name, Value, Req :: cowboy_req:req()) -&amp;gt; set_resp_cookie(Name, Value, Req, #{}) set_resp_cookie(Name, Value, Req :: cowboy_req:req(), Opts) -&amp;gt; Req Name :: binary() %% case sensitive Value :: iodata() %% case sensitive Opts :: cow_cookie:cookie_opts()  Set a cookie to be sent with the response.
Note that cookie names are case sensitive.
Arguments Name Cookie name.
 Value Cookie value.
 Req The Req object.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.set_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.set_resp_header/</guid>
      <description>Name cowboy_req:set_resp_header - Set a response header
Description set_resp_header(Name, Value, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive Value :: iodata() %% case depends on header  Set a header to be sent with the response.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.set_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.set_resp_header/</guid>
      <description>Name cowboy_req:set_resp_header - Set a response header
Description set_resp_header(Name, Value, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive Value :: iodata() %% case depends on header  Set a header to be sent with the response.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.set_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.set_resp_header/</guid>
      <description>Name cowboy_req:set_resp_header - Set a response header
Description set_resp_header(Name, Value, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive Value :: iodata() %% case depends on header  Set a header to be sent with the response.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.set_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.set_resp_header/</guid>
      <description>Name cowboy_req:set_resp_header - Set a response header
Description set_resp_header(Name, Value, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive Value :: iodata() %% case depends on header  Set a header to be sent with the response.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_header/</guid>
      <description>Name cowboy_req:set_resp_header - Set a response header
Description set_resp_header(Name, Value, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive Value :: iodata() %% case depends on header  Set a header to be sent with the response.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_header(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.set_resp_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.set_resp_header/</guid>
      <description>Name cowboy_req:set_resp_header - Set a response header
Description set_resp_header(Name, Value, Req :: cowboy_req:req()) -&amp;gt; Req Name :: binary() %% lowercase; case insensitive Value :: iodata() %% case depends on header  Set a header to be sent with the response.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.set_resp_headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.set_resp_headers/</guid>
      <description>Name cowboy_req:set_resp_headers - Set several response headers
Description set_resp_headers(Headers, Req :: cowboy_req:req()) -&amp;gt; Req Headers :: cowboy:http_headers()  Set several headers to be sent with the response.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names. Headers set by this function may be overwritten by those set from the reply functions.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.set_resp_headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.set_resp_headers/</guid>
      <description>Name cowboy_req:set_resp_headers - Set several response headers
Description set_resp_headers(Headers, Req :: cowboy_req:req()) -&amp;gt; Req Headers :: cowboy:http_headers()  Set several headers to be sent with the response.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names. Headers set by this function may be overwritten by those set from the reply functions.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.set_resp_headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.set_resp_headers/</guid>
      <description>Name cowboy_req:set_resp_headers - Set several response headers
Description set_resp_headers(Headers, Req :: cowboy_req:req()) -&amp;gt; Req Headers :: cowboy:http_headers()  Set several headers to be sent with the response.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names. Headers set by this function may be overwritten by those set from the reply functions.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.set_resp_headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.set_resp_headers/</guid>
      <description>Name cowboy_req:set_resp_headers - Set several response headers
Description set_resp_headers(Headers, Req :: cowboy_req:req()) -&amp;gt; Req Headers :: cowboy:http_headers()  Set several headers to be sent with the response.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names. Headers set by this function may be overwritten by those set from the reply functions.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.set_resp_headers/</guid>
      <description>Name cowboy_req:set_resp_headers - Set several response headers
Description set_resp_headers(Headers, Req :: cowboy_req:req()) -&amp;gt; Req Headers :: cowboy:http_headers()  Set several headers to be sent with the response.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names. Headers set by this function may be overwritten by those set from the reply functions.</description>
    </item>
    
    <item>
      <title>cowboy_req:set_resp_headers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.set_resp_headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.set_resp_headers/</guid>
      <description>Name cowboy_req:set_resp_headers - Set several response headers
Description set_resp_headers(Headers, Req :: cowboy_req:req()) -&amp;gt; Req Headers :: cowboy:http_headers()  Set several headers to be sent with the response.
The header name must be given as a lowercase binary string. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names. Headers set by this function may be overwritten by those set from the reply functions.</description>
    </item>
    
    <item>
      <title>cowboy_req:sock(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.sock/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.sock/</guid>
      <description>Name cowboy_req:sock - Socket address and port
Description sock(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the socket&amp;apos;s IP address and port number.
The socket information can also be obtained using pattern matching:
#{sock := {IP, Port}} = Req.  Arguments Req The Req object.
  Return value The socket&amp;apos;s local IP address and port number.
Changelog 2.1: Function introduced.   Examples Get the socket&amp;apos;s IP address and port number.</description>
    </item>
    
    <item>
      <title>cowboy_req:sock(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.sock/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.sock/</guid>
      <description>Name cowboy_req:sock - Socket address and port
Description sock(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the socket&amp;apos;s IP address and port number.
The socket information can also be obtained using pattern matching:
#{sock := {IP, Port}} = Req.  Arguments Req The Req object.
  Return value The socket&amp;apos;s local IP address and port number.
Changelog 2.1: Function introduced.   Examples Get the socket&amp;apos;s IP address and port number.</description>
    </item>
    
    <item>
      <title>cowboy_req:sock(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.sock/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.sock/</guid>
      <description>Name cowboy_req:sock - Socket address and port
Description sock(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the socket&amp;apos;s IP address and port number.
The socket information can also be obtained using pattern matching:
#{sock := {IP, Port}} = Req.  Arguments Req The Req object.
  Return value The socket&amp;apos;s local IP address and port number.
Changelog 2.1: Function introduced.   Examples Get the socket&amp;apos;s IP address and port number.</description>
    </item>
    
    <item>
      <title>cowboy_req:sock(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.sock/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.sock/</guid>
      <description>Name cowboy_req:sock - Socket address and port
Description sock(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the socket&amp;apos;s IP address and port number.
The socket information can also be obtained using pattern matching:
#{sock := {IP, Port}} = Req.  Arguments Req The Req object.
  Return value The socket&amp;apos;s local IP address and port number.
Changelog 2.1: Function introduced.   Examples Get the socket&amp;apos;s IP address and port number.</description>
    </item>
    
    <item>
      <title>cowboy_req:sock(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.sock/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.sock/</guid>
      <description>Name cowboy_req:sock - Socket address and port
Description sock(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the socket&amp;apos;s IP address and port number.
The socket information can also be obtained using pattern matching:
#{sock := {IP, Port}} = Req.  Arguments Req The Req object.
  Return value The socket&amp;apos;s local IP address and port number.
Changelog 2.1: Function introduced.   Examples Get the socket&amp;apos;s IP address and port number.</description>
    </item>
    
    <item>
      <title>cowboy_req:sock(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.sock/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.sock/</guid>
      <description>Name cowboy_req:sock - Socket address and port
Description sock(Req :: cowboy_req:req()) -&amp;gt; Info Info :: {inet:ip_address(), inet:port_number()}  Return the socket&amp;apos;s IP address and port number.
The socket information can also be obtained using pattern matching:
#{sock := {IP, Port}} = Req.  Arguments Req The Req object.
  Return value The socket&amp;apos;s local IP address and port number.
Changelog 2.1: Function introduced.   Examples Get the socket&amp;apos;s IP address and port number.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.stream_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.stream_body/</guid>
      <description>Name cowboy_req:stream_body - Stream the response body
Description stream_body(Data, IsFin, Req :: cowboy_req:req()) -&amp;gt; ok Data :: iodata() IsFin :: fin | nofin  Stream the response body.
This function may be called as many times as needed after initiating a response using the cowboy_req:stream_reply(3) function.
The second argument indicates if this call is the final call. Use the nofin value until you know no more data will be sent. The final call should use fin (possibly with an empty data value) or be a call to the cowboy_req:stream_trailers(3) function.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.stream_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.stream_body/</guid>
      <description>Name cowboy_req:stream_body - Stream the response body
Description stream_body(Data, IsFin, Req :: cowboy_req:req()) -&amp;gt; ok Data :: iodata() IsFin :: fin | nofin  Stream the response body.
This function may be called as many times as needed after initiating a response using the cowboy_req:stream_reply(3) function.
The second argument indicates if this call is the final call. Use the nofin value until you know no more data will be sent. The final call should use fin (possibly with an empty data value) or be a call to the cowboy_req:stream_trailers(3) function.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.stream_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.stream_body/</guid>
      <description>Name cowboy_req:stream_body - Stream the response body
Description stream_body(Data, IsFin, Req :: cowboy_req:req()) -&amp;gt; ok Data :: iodata() IsFin :: fin | nofin  Stream the response body.
This function may be called as many times as needed after initiating a response using the cowboy_req:stream_reply(3) function.
The second argument indicates if this call is the final call. Use the nofin value until you know no more data will be sent. The final call should use fin (possibly with an empty data value) or be a call to the cowboy_req:stream_trailers(3) function.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.stream_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.stream_body/</guid>
      <description>Name cowboy_req:stream_body - Stream the response body
Description stream_body(Data, IsFin, Req :: cowboy_req:req()) -&amp;gt; ok Data :: iodata() IsFin :: fin | nofin  Stream the response body.
This function may be called as many times as needed after initiating a response using the cowboy_req:stream_reply(3) function.
The second argument indicates if this call is the final call. Use the nofin value until you know no more data will be sent. The final call should use fin (possibly with an empty data value) or be a call to the cowboy_req:stream_trailers(3) function.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.stream_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.stream_body/</guid>
      <description>Name cowboy_req:stream_body - Stream the response body
Description stream_body(Data, IsFin, Req :: cowboy_req:req()) -&amp;gt; ok Data :: cowboy_req:resp_body() IsFin :: fin | nofin  Stream the response body.
This function may be called as many times as needed after initiating a response using the cowboy_req:stream_reply(3) function.
The second argument indicates if this call is the final call. Use the nofin value until you know no more data will be sent. The final call should use fin (possibly with an empty data value) or be a call to the cowboy_req:stream_trailers(3) function.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_body(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.stream_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.stream_body/</guid>
      <description>Name cowboy_req:stream_body - Stream the response body
Description stream_body(Data, IsFin, Req :: cowboy_req:req()) -&amp;gt; ok Data :: cowboy_req:resp_body() IsFin :: fin | nofin  Stream the response body.
This function may be called as many times as needed after initiating a response using the cowboy_req:stream_reply(3) function.
The second argument indicates if this call is the final call. Use the nofin value until you know no more data will be sent. The final call should use fin (possibly with an empty data value) or be a call to the cowboy_req:stream_trailers(3) function.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_events(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.stream_events/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.stream_events/</guid>
      <description>Name cowboy_req:stream_events - Stream events
Description stream_events(Events, IsFin, Req :: cowboy_req:req()) -&amp;gt; ok Events :: Event | [Event] IsFin :: fin | nofin Event :: #{ comment =&amp;gt; iodata(), data =&amp;gt; iodata(), event =&amp;gt; iodata() | atom(), id =&amp;gt; iodata(), retry =&amp;gt; non_neg_integer() }  Stream events.
This function should only be used for text/event-stream responses when using server-sent events. Cowboy will automatically encode the given events to their text representation.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_events(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.stream_events/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.stream_events/</guid>
      <description>Name cowboy_req:stream_events - Stream events
Description stream_events(Events, IsFin, Req :: cowboy_req:req()) -&amp;gt; ok Events :: Event | [Event] IsFin :: fin | nofin Event :: #{ comment =&amp;gt; iodata(), data =&amp;gt; iodata(), event =&amp;gt; iodata() | atom(), id =&amp;gt; iodata(), retry =&amp;gt; non_neg_integer() }  Stream events.
This function should only be used for text/event-stream responses when using server-sent events. Cowboy will automatically encode the given events to their text representation.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_events(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.stream_events/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.stream_events/</guid>
      <description>Name cowboy_req:stream_events - Stream events
Description stream_events(Events, IsFin, Req :: cowboy_req:req()) -&amp;gt; ok Events :: Event | [Event] IsFin :: fin | nofin Event :: #{ comment =&amp;gt; iodata(), data =&amp;gt; iodata(), event =&amp;gt; iodata() | atom(), id =&amp;gt; iodata(), retry =&amp;gt; non_neg_integer() }  Stream events.
This function should only be used for text/event-stream responses when using server-sent events. Cowboy will automatically encode the given events to their text representation.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_reply(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.stream_reply/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.stream_reply/</guid>
      <description>Name cowboy_req:stream_reply - Send the response headers
Description stream_reply(Status, Req :: cowboy_req:req()) -&amp;gt; stream_reply(StatusCode, #{}, Req) stream_reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send the response headers.
The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names. Headers set by this function may overwrite those set by set_resp_header/3.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_reply(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.stream_reply/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.stream_reply/</guid>
      <description>Name cowboy_req:stream_reply - Send the response headers
Description stream_reply(Status, Req :: cowboy_req:req()) -&amp;gt; stream_reply(StatusCode, #{}, Req) stream_reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send the response headers.
The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names. Headers set by this function may overwrite those set by set_resp_header/3.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_reply(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.stream_reply/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.stream_reply/</guid>
      <description>Name cowboy_req:stream_reply - Send the response headers
Description stream_reply(Status, Req :: cowboy_req:req()) -&amp;gt; stream_reply(StatusCode, #{}, Req) stream_reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send the response headers.
The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names. Headers set by this function may overwrite those set by set_resp_header/3.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_reply(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.stream_reply/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.stream_reply/</guid>
      <description>Name cowboy_req:stream_reply - Send the response headers
Description stream_reply(Status, Req :: cowboy_req:req()) -&amp;gt; stream_reply(StatusCode, #{}, Req) stream_reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send the response headers.
The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names. Headers set by this function may overwrite those set by set_resp_header/3.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_reply(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.stream_reply/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.stream_reply/</guid>
      <description>Name cowboy_req:stream_reply - Send the response headers
Description stream_reply(Status, Req :: cowboy_req:req()) -&amp;gt; stream_reply(StatusCode, #{}, Req) stream_reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send the response headers.
The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names. Headers set by this function may overwrite those set by set_resp_header/3.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_reply(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.stream_reply/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.stream_reply/</guid>
      <description>Name cowboy_req:stream_reply - Send the response headers
Description stream_reply(Status, Req :: cowboy_req:req()) -&amp;gt; stream_reply(StatusCode, #{}, Req) stream_reply(Status, Headers, Req :: cowboy_req:req()) -&amp;gt; Req Status :: cowboy:http_status() Headers :: cowboy:http_headers()  Send the response headers.
The header names must be given as lowercase binary strings. While header names are case insensitive, Cowboy requires them to be given as lowercase to function properly.
Cowboy does not allow duplicate header names. Headers set by this function may overwrite those set by set_resp_header/3.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_trailers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.stream_trailers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.stream_trailers/</guid>
      <description>Name cowboy_req:stream_trailers - Send the response trailers
Description stream_trailers(Trailers, Req :: cowboy_req:req()) -&amp;gt; ok Trailers :: cowboy:http_headers()  Send the response trailers and terminate the stream.
This function can only be called once, after initiating a response using cowboy_req:stream_reply(3) and sending zero or more body chunks using cowboy_req:stream_body(3) with the nofin argument set. The function stream_trailers/2 implies fin and automatically terminate the response.
You must list all field names sent in trailers in the trailer header, otherwise they might be dropped by intermediaries or clients.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_trailers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.stream_trailers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.stream_trailers/</guid>
      <description>Name cowboy_req:stream_trailers - Send the response trailers
Description stream_trailers(Trailers, Req :: cowboy_req:req()) -&amp;gt; ok Trailers :: cowboy:http_headers()  Send the response trailers and terminate the stream.
This function can only be called once, after initiating a response using cowboy_req:stream_reply(3) and sending zero or more body chunks using cowboy_req:stream_body(3) with the nofin argument set. The function stream_trailers/2 implies fin and automatically terminate the response.
You must list all field names sent in trailers in the trailer header, otherwise they might be dropped by intermediaries or clients.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_trailers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.stream_trailers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.stream_trailers/</guid>
      <description>Name cowboy_req:stream_trailers - Send the response trailers
Description stream_trailers(Trailers, Req :: cowboy_req:req()) -&amp;gt; ok Trailers :: cowboy:http_headers()  Send the response trailers and terminate the stream.
This function can only be called once, after initiating a response using cowboy_req:stream_reply(3) and sending zero or more body chunks using cowboy_req:stream_body(3) with the nofin argument set. The function stream_trailers/2 implies fin and automatically terminate the response.
You must list all field names sent in trailers in the trailer header, otherwise they might be dropped by intermediaries or clients.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_trailers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.stream_trailers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.stream_trailers/</guid>
      <description>Name cowboy_req:stream_trailers - Send the response trailers
Description stream_trailers(Trailers, Req :: cowboy_req:req()) -&amp;gt; ok Trailers :: cowboy:http_headers()  Send the response trailers and terminate the stream.
This function can only be called once, after initiating a response using cowboy_req:stream_reply(3) and sending zero or more body chunks using cowboy_req:stream_body(3) with the nofin argument set. The function stream_trailers/2 implies fin and automatically terminate the response.
You must list all field names sent in trailers in the trailer header, otherwise they might be dropped by intermediaries or clients.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_trailers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.stream_trailers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.stream_trailers/</guid>
      <description>Name cowboy_req:stream_trailers - Send the response trailers
Description stream_trailers(Trailers, Req :: cowboy_req:req()) -&amp;gt; ok Trailers :: cowboy:http_headers()  Send the response trailers and terminate the stream.
This function can only be called once, after initiating a response using cowboy_req:stream_reply(3) and sending zero or more body chunks using cowboy_req:stream_body(3) with the nofin argument set. The function stream_trailers/2 implies fin and automatically terminate the response.
You must list all field names sent in trailers in the trailer header, otherwise they might be dropped by intermediaries or clients.</description>
    </item>
    
    <item>
      <title>cowboy_req:stream_trailers(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.stream_trailers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.stream_trailers/</guid>
      <description>Name cowboy_req:stream_trailers - Send the response trailers
Description stream_trailers(Trailers, Req :: cowboy_req:req()) -&amp;gt; ok Trailers :: cowboy:http_headers()  Send the response trailers and terminate the stream.
This function can only be called once, after initiating a response using cowboy_req:stream_reply(3) and sending zero or more body chunks using cowboy_req:stream_body(3) with the nofin argument set. The function stream_trailers/2 implies fin and automatically terminate the response.
You must list all field names sent in trailers in the trailer header, otherwise they might be dropped by intermediaries or clients.</description>
    </item>
    
    <item>
      <title>cowboy_req:uri(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.uri/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.uri/</guid>
      <description>Name cowboy_req:uri - Reconstructed URI
Description uri(Req :: cowboy_req:req()) -&amp;gt; uri(Req, #{}) uri(Req :: cowboy_req:req(), Opts) -&amp;gt; URI :: iodata() Opts :: #{ scheme =&amp;gt; iodata() | undefined, host =&amp;gt; iodata() | undefined, port =&amp;gt; inet:port_number() | undefined, path =&amp;gt; iodata() | undefined, qs =&amp;gt; iodata() | undefined, fragment =&amp;gt; iodata() | undefined }  Reconstruct the effective request URI, optionally modifying components.
By default Cowboy will build a URI using the components found in the request.</description>
    </item>
    
    <item>
      <title>cowboy_req:uri(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.uri/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.uri/</guid>
      <description>Name cowboy_req:uri - Reconstructed URI
Description uri(Req :: cowboy_req:req()) -&amp;gt; uri(Req, #{}) uri(Req :: cowboy_req:req(), Opts) -&amp;gt; URI :: iodata() Opts :: #{ scheme =&amp;gt; iodata() | undefined, host =&amp;gt; iodata() | undefined, port =&amp;gt; inet:port_number() | undefined, path =&amp;gt; iodata() | undefined, qs =&amp;gt; iodata() | undefined, fragment =&amp;gt; iodata() | undefined }  Reconstruct the effective request URI, optionally modifying components.
By default Cowboy will build a URI using the components found in the request.</description>
    </item>
    
    <item>
      <title>cowboy_req:uri(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.uri/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.uri/</guid>
      <description>Name cowboy_req:uri - Reconstructed URI
Description uri(Req :: cowboy_req:req()) -&amp;gt; uri(Req, #{}) uri(Req :: cowboy_req:req(), Opts) -&amp;gt; URI :: iodata() Opts :: #{ scheme =&amp;gt; iodata() | undefined, host =&amp;gt; iodata() | undefined, port =&amp;gt; inet:port_number() | undefined, path =&amp;gt; iodata() | undefined, qs =&amp;gt; iodata() | undefined, fragment =&amp;gt; iodata() | undefined }  Reconstruct the effective request URI, optionally modifying components.
By default Cowboy will build a URI using the components found in the request.</description>
    </item>
    
    <item>
      <title>cowboy_req:uri(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.uri/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.uri/</guid>
      <description>Name cowboy_req:uri - Reconstructed URI
Description uri(Req :: cowboy_req:req()) -&amp;gt; uri(Req, #{}) uri(Req :: cowboy_req:req(), Opts) -&amp;gt; URI :: iodata() Opts :: #{ scheme =&amp;gt; iodata() | undefined, host =&amp;gt; iodata() | undefined, port =&amp;gt; inet:port_number() | undefined, path =&amp;gt; iodata() | undefined, qs =&amp;gt; iodata() | undefined, fragment =&amp;gt; iodata() | undefined }  Reconstruct the effective request URI, optionally modifying components.
By default Cowboy will build a URI using the components found in the request.</description>
    </item>
    
    <item>
      <title>cowboy_req:uri(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.uri/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.uri/</guid>
      <description>Name cowboy_req:uri - Reconstructed URI
Description uri(Req :: cowboy_req:req()) -&amp;gt; uri(Req, #{}) uri(Req :: cowboy_req:req(), Opts) -&amp;gt; URI :: iodata() Opts :: #{ scheme =&amp;gt; iodata() | undefined, host =&amp;gt; iodata() | undefined, port =&amp;gt; inet:port_number() | undefined, path =&amp;gt; iodata() | undefined, qs =&amp;gt; iodata() | undefined, fragment =&amp;gt; iodata() | undefined }  Reconstruct the effective request URI, optionally modifying components.
By default Cowboy will build a URI using the components found in the request.</description>
    </item>
    
    <item>
      <title>cowboy_req:uri(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.uri/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.uri/</guid>
      <description>Name cowboy_req:uri - Reconstructed URI
Description uri(Req :: cowboy_req:req()) -&amp;gt; uri(Req, #{}) uri(Req :: cowboy_req:req(), Opts) -&amp;gt; URI :: iodata() Opts :: #{ scheme =&amp;gt; iodata() | undefined, host =&amp;gt; iodata() | undefined, port =&amp;gt; inet:port_number() | undefined, path =&amp;gt; iodata() | undefined, qs =&amp;gt; iodata() | undefined, fragment =&amp;gt; iodata() | undefined }  Reconstruct the effective request URI, optionally modifying components.
By default Cowboy will build a URI using the components found in the request.</description>
    </item>
    
    <item>
      <title>cowboy_req:version(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.version/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_req.version/</guid>
      <description>Name cowboy_req:version - HTTP version
Description version(Req :: cowboy_req:req()) -&amp;gt; Version :: cowboy:http_version()  Return the HTTP version used for the request.
The version can also be obtained using pattern matching:
#{version := Version} = Req.  Arguments Req The Req object.
  Return value The HTTP version used for the request is returned as an atom. It is provided for informative purposes only.
Changelog 2.0: Only the version is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:version(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.version/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_req.version/</guid>
      <description>Name cowboy_req:version - HTTP version
Description version(Req :: cowboy_req:req()) -&amp;gt; Version :: cowboy:http_version()  Return the HTTP version used for the request.
The version can also be obtained using pattern matching:
#{version := Version} = Req.  Arguments Req The Req object.
  Return value The HTTP version used for the request is returned as an atom. It is provided for informative purposes only.
Changelog 2.0: Only the version is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:version(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.version/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_req.version/</guid>
      <description>Name cowboy_req:version - HTTP version
Description version(Req :: cowboy_req:req()) -&amp;gt; Version :: cowboy:http_version()  Return the HTTP version used for the request.
The version can also be obtained using pattern matching:
#{version := Version} = Req.  Arguments Req The Req object.
  Return value The HTTP version used for the request is returned as an atom. It is provided for informative purposes only.
Changelog 2.0: Only the version is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:version(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.version/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_req.version/</guid>
      <description>Name cowboy_req:version - HTTP version
Description version(Req :: cowboy_req:req()) -&amp;gt; Version :: cowboy:http_version()  Return the HTTP version used for the request.
The version can also be obtained using pattern matching:
#{version := Version} = Req.  Arguments Req The Req object.
  Return value The HTTP version used for the request is returned as an atom. It is provided for informative purposes only.
Changelog 2.0: Only the version is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:version(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.version/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_req.version/</guid>
      <description>Name cowboy_req:version - HTTP version
Description version(Req :: cowboy_req:req()) -&amp;gt; Version :: cowboy:http_version()  Return the HTTP version used for the request.
The version can also be obtained using pattern matching:
#{version := Version} = Req.  Arguments Req The Req object.
  Return value The HTTP version used for the request is returned as an atom. It is provided for informative purposes only.
Changelog 2.0: Only the version is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_req:version(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.version/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_req.version/</guid>
      <description>Name cowboy_req:version - HTTP version
Description version(Req :: cowboy_req:req()) -&amp;gt; Version :: cowboy:http_version()  Return the HTTP version used for the request.
The version can also be obtained using pattern matching:
#{version := Version} = Req.  Arguments Req The Req object.
  Return value The HTTP version used for the request is returned as an atom. It is provided for informative purposes only.
Changelog 2.0: Only the version is returned, it is no longer wrapped in a tuple.</description>
    </item>
    
    <item>
      <title>cowboy_rest(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_rest/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_rest/</guid>
      <description>Name cowboy_rest - REST handlers
Description The module cowboy_rest implements the HTTP state machine.
Implementing REST handlers is not enough to provide a REST interface; this interface must also follow the REST constraints including HATEOAS (hypermedia as the engine of application state).
Callbacks REST handlers implement the following interface:
init(Req, State) -&amp;gt; {cowboy_rest, Req, State} Callback(Req, State) -&amp;gt; {Result, Req, State} | {stop, Req, State} | {{switch_handler, Module}, Req, State} | {{switch_handler, Module, Opts}, Req, State} terminate(Reason, Req, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() State :: any() Module :: module() Opts :: any() Reason :: normal | {crash, error | exit | throw, any()} Callback - see below Result - see below Default - see below  The init/2 callback is common to all handlers.</description>
    </item>
    
    <item>
      <title>cowboy_rest(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_rest/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_rest/</guid>
      <description>Name cowboy_rest - REST handlers
Description The module cowboy_rest implements the HTTP state machine.
Implementing REST handlers is not enough to provide a REST interface; this interface must also follow the REST constraints including HATEOAS (hypermedia as the engine of application state).
Callbacks REST handlers implement the following interface:
init(Req, State) -&amp;gt; {cowboy_rest, Req, State} Callback(Req, State) -&amp;gt; {Result, Req, State} | {stop, Req, State} | {{switch_handler, Module}, Req, State} | {{switch_handler, Module, Opts}, Req, State} terminate(Reason, Req, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() State :: any() Module :: module() Opts :: any() Reason :: normal | {crash, error | exit | throw, any()} Callback - see below Result - see below Default - see below  The init/2 callback is common to all handlers.</description>
    </item>
    
    <item>
      <title>cowboy_rest(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_rest/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_rest/</guid>
      <description>Name cowboy_rest - REST handlers
Description The module cowboy_rest implements the HTTP state machine.
Implementing REST handlers is not enough to provide a REST interface; this interface must also follow the REST constraints including HATEOAS (hypermedia as the engine of application state).
Callbacks REST handlers implement the following interface:
init(Req, State) -&amp;gt; {cowboy_rest, Req, State} Callback(Req, State) -&amp;gt; {Result, Req, State} | {stop, Req, State} | {{switch_handler, Module}, Req, State} | {{switch_handler, Module, Opts}, Req, State} terminate(Reason, Req, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() State :: any() Module :: module() Opts :: any() Reason :: normal | {crash, error | exit | throw, any()} Callback - see below Result - see below Default - see below  The init/2 callback is common to all handlers.</description>
    </item>
    
    <item>
      <title>cowboy_rest(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_rest/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_rest/</guid>
      <description>Name cowboy_rest - REST handlers
Description The module cowboy_rest implements the HTTP state machine.
Implementing REST handlers is not enough to provide a REST interface; this interface must also follow the REST constraints including HATEOAS (hypermedia as the engine of application state).
Callbacks REST handlers implement the following interface:
init(Req, State) -&amp;gt; {cowboy_rest, Req, State} Callback(Req, State) -&amp;gt; {Result, Req, State} | {stop, Req, State} | {{switch_handler, Module}, Req, State} | {{switch_handler, Module, Opts}, Req, State} terminate(Reason, Req, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() State :: any() Module :: module() Opts :: any() Reason :: normal | {crash, error | exit | throw, any()} Callback - see below Result - see below Default - see below  The init/2 callback is common to all handlers.</description>
    </item>
    
    <item>
      <title>cowboy_rest(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_rest/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_rest/</guid>
      <description>Name cowboy_rest - REST handlers
Description The module cowboy_rest implements the HTTP state machine.
Implementing REST handlers is not enough to provide a REST interface; this interface must also follow the REST constraints including HATEOAS (hypermedia as the engine of application state).
Callbacks REST handlers implement the following interface:
init(Req, State) -&amp;gt; {cowboy_rest, Req, State} Callback(Req, State) -&amp;gt; {Result, Req, State} | {stop, Req, State} | {{switch_handler, Module}, Req, State} | {{switch_handler, Module, Opts}, Req, State} terminate(Reason, Req, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() State :: any() Module :: module() Opts :: any() Reason :: normal | {crash, error | exit | throw, any()} Callback - see below Result - see below Default - see below  The init/2 callback is common to all handlers.</description>
    </item>
    
    <item>
      <title>cowboy_rest(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_rest/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_rest/</guid>
      <description>Name cowboy_rest - REST handlers
Description The module cowboy_rest implements the HTTP state machine.
Implementing REST handlers is not enough to provide a REST interface; this interface must also follow the REST constraints including HATEOAS (hypermedia as the engine of application state).
Callbacks REST handlers implement the following interface:
init(Req, State) -&amp;gt; {cowboy_rest, Req, State} Callback(Req, State) -&amp;gt; {Result, Req, State} | {stop, Req, State} | {{switch_handler, Module}, Req, State} | {{switch_handler, Module, Opts}, Req, State} terminate(Reason, Req, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() State :: any() Module :: module() Opts :: any() Reason :: normal | {crash, error | exit | throw, any()} Callback - see below Result - see below Default - see below  The init/2 callback is common to all handlers.</description>
    </item>
    
    <item>
      <title>cowboy_router(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_router/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_router/</guid>
      <description>Name cowboy_router - Router middleware
Description The cowboy_router middleware maps the requested host and path to the handler to be used for processing the request.
The router takes the dispatch rules as input from the middleware environment. Dispatch rules are generated by calling the cowboy_router:compile(3) function.
When a route matches, the router sets the handler and handler_opts middleware environment values containing the handler module and initial state, respectively.
The router will stop execution when no route matches.</description>
    </item>
    
    <item>
      <title>cowboy_router(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_router/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_router/</guid>
      <description>Name cowboy_router - Router middleware
Description The cowboy_router middleware maps the requested host and path to the handler to be used for processing the request.
The router takes the dispatch rules as input from the middleware environment. Dispatch rules are generated by calling the cowboy_router:compile(3) function.
When a route matches, the router sets the handler and handler_opts middleware environment values containing the handler module and initial state, respectively.
The router will stop execution when no route matches.</description>
    </item>
    
    <item>
      <title>cowboy_router(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_router/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_router/</guid>
      <description>Name cowboy_router - Router middleware
Description The cowboy_router middleware maps the requested host and path to the handler to be used for processing the request.
The router takes the dispatch rules as input from the middleware environment. Dispatch rules are generated by calling the cowboy_router:compile(3) function.
When a route matches, the router sets the handler and handler_opts middleware environment values containing the handler module and initial state, respectively.
The router will stop execution when no route matches.</description>
    </item>
    
    <item>
      <title>cowboy_router(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_router/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_router/</guid>
      <description>Name cowboy_router - Router middleware
Description The cowboy_router middleware maps the requested host and path to the handler to be used for processing the request.
The router takes the dispatch rules as input from the middleware environment. Dispatch rules are generated by calling the cowboy_router:compile(3) function.
When a route matches, the router sets the handler and handler_opts middleware environment values containing the handler module and initial state, respectively.
The router will stop execution when no route matches.</description>
    </item>
    
    <item>
      <title>cowboy_router(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_router/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_router/</guid>
      <description>Name cowboy_router - Router middleware
Description The cowboy_router middleware maps the requested host and path to the handler to be used for processing the request.
The router takes the dispatch rules as input from the middleware environment. Dispatch rules are generated by calling the cowboy_router:compile(3) function.
When a route matches, the router sets the handler and handler_opts middleware environment values containing the handler module and initial state, respectively.
The router will stop execution when no route matches.</description>
    </item>
    
    <item>
      <title>cowboy_router(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_router/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_router/</guid>
      <description>Name cowboy_router - Router middleware
Description The cowboy_router middleware maps the requested host and path to the handler to be used for processing the request.
The router takes the dispatch rules as input from the middleware environment. Dispatch rules are generated by calling the cowboy_router:compile(3) function. The environment can contain the rules directly or a tuple {persistent_term, Key}, in which case Cowboy will call persistent_term:get(Key) to retrieve the dispatch rules.</description>
    </item>
    
    <item>
      <title>cowboy_router:compile(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_router.compile/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_router.compile/</guid>
      <description>Name cowboy_router:compile - Compile routes to the resources
Description compile(cowboy_router:routes()) -&amp;gt; cowboy_router:dispatch_rules()  Compile routes to the resources.
Takes a human readable list of routes and transforms it into a form more efficient to process.
Arguments Routes Human readable list of routes.
  Return value An opaque dispatch rules value is returned. This value must be given to Cowboy as a middleware environment value.
Changelog 1.0: Function introduced.   Examples Compile routes and start a listener Dispatch = cowboy_router:compile([ {&#39;_&#39;, [ {&#34;</description>
    </item>
    
    <item>
      <title>cowboy_router:compile(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_router.compile/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_router.compile/</guid>
      <description>Name cowboy_router:compile - Compile routes to the resources
Description compile(cowboy_router:routes()) -&amp;gt; cowboy_router:dispatch_rules()  Compile routes to the resources.
Takes a human readable list of routes and transforms it into a form more efficient to process.
Arguments Routes Human readable list of routes.
  Return value An opaque dispatch rules value is returned. This value must be given to Cowboy as a middleware environment value.
Changelog 1.0: Function introduced.   Examples Compile routes and start a listener Dispatch = cowboy_router:compile([ {&#39;_&#39;, [ {&#34;</description>
    </item>
    
    <item>
      <title>cowboy_router:compile(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_router.compile/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_router.compile/</guid>
      <description>Name cowboy_router:compile - Compile routes to the resources
Description compile(cowboy_router:routes()) -&amp;gt; cowboy_router:dispatch_rules()  Compile routes to the resources.
Takes a human readable list of routes and transforms it into a form more efficient to process.
Arguments Routes Human readable list of routes.
  Return value An opaque dispatch rules value is returned. This value must be given to Cowboy as a middleware environment value.
Changelog 1.0: Function introduced.   Examples Compile routes and start a listener Dispatch = cowboy_router:compile([ {&#39;_&#39;, [ {&#34;</description>
    </item>
    
    <item>
      <title>cowboy_router:compile(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_router.compile/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_router.compile/</guid>
      <description>Name cowboy_router:compile - Compile routes to the resources
Description compile(cowboy_router:routes()) -&amp;gt; cowboy_router:dispatch_rules()  Compile routes to the resources.
Takes a human readable list of routes and transforms it into a form more efficient to process.
Arguments Routes Human readable list of routes.
  Return value An opaque dispatch rules value is returned. This value must be given to Cowboy as a middleware environment value.
Changelog 1.0: Function introduced.   Examples Compile routes and start a listener Dispatch = cowboy_router:compile([ {&#39;_&#39;, [ {&#34;</description>
    </item>
    
    <item>
      <title>cowboy_router:compile(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_router.compile/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_router.compile/</guid>
      <description>Name cowboy_router:compile - Compile routes to the resources
Description compile(cowboy_router:routes()) -&amp;gt; cowboy_router:dispatch_rules()  Compile routes to the resources.
Takes a human readable list of routes and transforms it into a form more efficient to process.
Arguments Routes Human readable list of routes.
  Return value An opaque dispatch rules value is returned. This value must be given to Cowboy as a middleware environment value.
Changelog 1.0: Function introduced.   Examples Compile routes and start a listener Dispatch = cowboy_router:compile([ {&#39;_&#39;, [ {&#34;</description>
    </item>
    
    <item>
      <title>cowboy_router:compile(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_router.compile/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_router.compile/</guid>
      <description>Name cowboy_router:compile - Compile routes to the resources
Description compile(cowboy_router:routes()) -&amp;gt; cowboy_router:dispatch_rules()  Compile routes to the resources.
Takes a human readable list of routes and transforms it into a form more efficient to process.
Arguments Routes Human readable list of routes.
  Return value An opaque dispatch rules value is returned. This value must be given to Cowboy as a middleware environment value.
Changelog 1.0: Function introduced.   Examples Compile routes and start a listener Dispatch = cowboy_router:compile([ {&#39;_&#39;, [ {&#34;</description>
    </item>
    
    <item>
      <title>cowboy_static(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_static/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_static/</guid>
      <description>Name cowboy_static - Static file handler
Description The module cowboy_static implements file serving capabilities using the REST semantics provided by cowboy_rest.
The static file handler is a pre-written handler coming with Cowboy. To serve files, use it in your routes.
Options opts() :: {priv_file, App, Path} | {priv_file, App, Path, Extra} | {file, Path} | {file, Path, Extra} | {priv_dir, App, Path} | {priv_dir, App, Path, Extra} | {dir, Path} | {dir, Path, Extra} App :: atom() Path :: binary() | string() Extra :: [Etag | Mimetypes] Etag :: {etag, module(), function()} | {etag, false} Mimetypes :: {mimetypes, module(), function()} | {mimetypes, binary() | ParsedMime} ParsedMime :: {Type :: binary(), SubType :: binary(), Params} Params :: [{Key :: binary(), Value :: binary()}]  Static handler configuration.</description>
    </item>
    
    <item>
      <title>cowboy_static(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_static/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_static/</guid>
      <description>Name cowboy_static - Static file handler
Description The module cowboy_static implements file serving capabilities using the REST semantics provided by cowboy_rest.
The static file handler is a pre-written handler coming with Cowboy. To serve files, use it in your routes.
Options opts() :: {priv_file, App, Path} | {priv_file, App, Path, Extra} | {file, Path} | {file, Path, Extra} | {priv_dir, App, Path} | {priv_dir, App, Path, Extra} | {dir, Path} | {dir, Path, Extra} App :: atom() Path :: binary() | string() Extra :: [Etag | Mimetypes] Etag :: {etag, module(), function()} | {etag, false} Mimetypes :: {mimetypes, module(), function()} | {mimetypes, binary() | ParsedMime} ParsedMime :: {Type :: binary(), SubType :: binary(), Params} Params :: [{Key :: binary(), Value :: binary()}]  Static handler configuration.</description>
    </item>
    
    <item>
      <title>cowboy_static(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_static/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_static/</guid>
      <description>Name cowboy_static - Static file handler
Description The module cowboy_static implements file serving capabilities using the REST semantics provided by cowboy_rest.
The static file handler is a pre-written handler coming with Cowboy. To serve files, use it in your routes.
Options opts() :: {priv_file, App, Path} | {priv_file, App, Path, Extra} | {file, Path} | {file, Path, Extra} | {priv_dir, App, Path} | {priv_dir, App, Path, Extra} | {dir, Path} | {dir, Path, Extra} App :: atom() Path :: binary() | string() Extra :: [Etag | Mimetypes] Etag :: {etag, module(), function()} | {etag, false} Mimetypes :: {mimetypes, module(), function()} | {mimetypes, binary() | ParsedMime} ParsedMime :: {Type :: binary(), SubType :: binary(), Params} Params :: [{Key :: binary(), Value :: binary()}]  Static handler configuration.</description>
    </item>
    
    <item>
      <title>cowboy_static(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_static/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_static/</guid>
      <description>Name cowboy_static - Static file handler
Description The module cowboy_static implements file serving capabilities using the REST semantics provided by cowboy_rest.
The static file handler is a pre-written handler coming with Cowboy. To serve files, use it in your routes.
Options opts() :: {priv_file, App, Path} | {priv_file, App, Path, Extra} | {file, Path} | {file, Path, Extra} | {priv_dir, App, Path} | {priv_dir, App, Path, Extra} | {dir, Path} | {dir, Path, Extra} App :: atom() Path :: binary() | string() Extra :: [Etag | Mimetypes] Etag :: {etag, module(), function()} | {etag, false} Mimetypes :: {mimetypes, module(), function()} | {mimetypes, binary() | ParsedMime} ParsedMime :: {Type :: binary(), SubType :: binary(), Params} Params :: [{Key :: binary(), Value :: binary()}]  Static handler configuration.</description>
    </item>
    
    <item>
      <title>cowboy_static(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_static/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_static/</guid>
      <description>Name cowboy_static - Static file handler
Description The module cowboy_static implements file serving capabilities using the REST semantics provided by cowboy_rest.
The static file handler is a pre-written handler coming with Cowboy. To serve files, use it in your routes.
Options opts() :: {priv_file, App, Path} | {priv_file, App, Path, Extra} | {file, Path} | {file, Path, Extra} | {priv_dir, App, Path} | {priv_dir, App, Path, Extra} | {dir, Path} | {dir, Path, Extra} App :: atom() Path :: binary() | string() Extra :: [Charset | Etag | Mimetypes] Charset :: {charset, module(), function()} | {charset, binary()} Etag :: {etag, module(), function()} | {etag, false} Mimetypes :: {mimetypes, module(), function()} | {mimetypes, binary() | ParsedMime} ParsedMime :: {Type :: binary(), SubType :: binary(), Params} Params :: [{Key :: binary(), Value :: binary()}]  Static handler configuration.</description>
    </item>
    
    <item>
      <title>cowboy_static(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_static/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_static/</guid>
      <description>Name cowboy_static - Static file handler
Description The module cowboy_static implements file serving capabilities using the REST semantics provided by cowboy_rest.
The static file handler is a pre-written handler coming with Cowboy. To serve files, use it in your routes.
Options opts() :: {priv_file, App, Path} | {priv_file, App, Path, Extra} | {file, Path} | {file, Path, Extra} | {priv_dir, App, Path} | {priv_dir, App, Path, Extra} | {dir, Path} | {dir, Path, Extra} App :: atom() Path :: binary() | string() Extra :: [Charset | Etag | Mimetypes] Charset :: {charset, module(), function()} | {charset, binary()} Etag :: {etag, module(), function()} | {etag, false} Mimetypes :: {mimetypes, module(), function()} | {mimetypes, binary() | ParsedMime} ParsedMime :: {Type :: binary(), SubType :: binary(), Params} Params :: [{Key :: binary(), Value :: binary()}]  Static handler configuration.</description>
    </item>
    
    <item>
      <title>cowboy_stream(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_stream/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_stream/</guid>
      <description>Name cowboy_handler - Stream handlers
Description The module cowboy_stream defines a callback interface and a protocol for handling HTTP streams.
An HTTP request and its associated response is called a stream. A connection may have many streams. In HTTP/1.1 they are executed sequentially, while in HTTP/2 they are executed concurrently.
Cowboy calls the stream handler for nearly all events related to a stream. Exceptions vary depending on the protocol.
Extra care must be taken when implementing stream handlers to ensure compatibility.</description>
    </item>
    
    <item>
      <title>cowboy_stream(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_stream/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_stream/</guid>
      <description>Name cowboy_handler - Stream handlers
Description The module cowboy_stream defines a callback interface and a protocol for handling HTTP streams.
An HTTP request and its associated response is called a stream. A connection may have many streams. In HTTP/1.1 they are executed sequentially, while in HTTP/2 they are executed concurrently.
Cowboy calls the stream handler for nearly all events related to a stream. Exceptions vary depending on the protocol.
Extra care must be taken when implementing stream handlers to ensure compatibility.</description>
    </item>
    
    <item>
      <title>cowboy_stream(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_stream/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_stream/</guid>
      <description>Name cowboy_handler - Stream handlers
Description The module cowboy_stream defines a callback interface and a protocol for handling HTTP streams.
An HTTP request and its associated response is called a stream. A connection may have many streams. In HTTP/1.1 they are executed sequentially, while in HTTP/2 they are executed concurrently.
Cowboy calls the stream handler for nearly all events related to a stream. Exceptions vary depending on the protocol.
Extra care must be taken when implementing stream handlers to ensure compatibility.</description>
    </item>
    
    <item>
      <title>cowboy_stream(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_stream/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_stream/</guid>
      <description>Name cowboy_stream - Stream handlers
Description The module cowboy_stream defines a callback interface and a protocol for handling HTTP streams.
An HTTP request and its associated response is called a stream. A connection may have many streams. In HTTP/1.1 they are executed sequentially, while in HTTP/2 they are executed concurrently.
Cowboy calls the stream handler for nearly all events related to a stream. Exceptions vary depending on the protocol.
Extra care must be taken when implementing stream handlers to ensure compatibility.</description>
    </item>
    
    <item>
      <title>cowboy_stream(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_stream/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_stream/</guid>
      <description>Name cowboy_stream - Stream handlers
Description The module cowboy_stream defines a callback interface and a protocol for handling HTTP streams.
An HTTP request and its associated response is called a stream. A connection may have many streams. In HTTP/1.1 they are executed sequentially, while in HTTP/2 they are executed concurrently.
Cowboy calls the stream handler for nearly all events related to a stream. Exceptions vary depending on the protocol.
Extra care must be taken when implementing stream handlers to ensure compatibility.</description>
    </item>
    
    <item>
      <title>cowboy_stream(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_stream/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_stream/</guid>
      <description>Name cowboy_stream - Stream handlers
Description The module cowboy_stream defines a callback interface and a protocol for handling HTTP streams.
An HTTP request and its associated response is called a stream. A connection may have many streams. In HTTP/1.1 they are executed sequentially, while in HTTP/2 they are executed concurrently.
Cowboy calls the stream handler for nearly all events related to a stream. Exceptions vary depending on the protocol.
Extra care must be taken when implementing stream handlers to ensure compatibility.</description>
    </item>
    
    <item>
      <title>cowboy_stream_h(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_stream_h/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_stream_h/</guid>
      <description>Name cowboy_stream_h - Default stream handler
Description The module cowboy_stream_h is Cowboy&amp;apos;s default stream handler and defines much of its behavior. It is responsible for managing the request process, sending it the request body and translating its messages into commands that Cowboy understands.
Options opts() :: #{ env =&amp;gt; cowboy_middleware:env(), middlewares =&amp;gt; [module()], shutdown_timeout =&amp;gt; timeout() }  Configuration for the default stream handler.
The default value is given next to the option name:</description>
    </item>
    
    <item>
      <title>cowboy_stream_h(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_stream_h/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_stream_h/</guid>
      <description>Name cowboy_stream_h - Default stream handler
Description The module cowboy_stream_h is Cowboy&amp;apos;s default stream handler and defines much of its behavior. It is responsible for managing the request process, sending it the request body and translating its messages into commands that Cowboy understands.
Options opts() :: #{ env =&amp;gt; cowboy_middleware:env(), middlewares =&amp;gt; [module()], shutdown_timeout =&amp;gt; timeout() }  Configuration for the default stream handler.
The default value is given next to the option name:</description>
    </item>
    
    <item>
      <title>cowboy_tracer_h(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_tracer_h/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_tracer_h/</guid>
      <description>Name cowboy_tracer_h - Tracer stream handler
Description The module cowboy_tracer_h can be used to conditionally trace streams based on information found in the request. Trace messages are given to the configured callback.
Options opts() :: #{ tracer_callback =&amp;gt; Callback, tracer_flags =&amp;gt; [atom()], tracer_match_specs =&amp;gt; [MatchSpec] } Callback :: fun((init | terminate | tuple(), State) -&amp;gt; State) MatchSpec :: MatchPredicate | {method, binary()} | {host, binary()} | {path, binary()} | {path_start, binary()} | {header, binary()} | {header, binary(), binary()} | {peer_ip, inet:ip_address()} MatchPredicate :: fun((cowboy_stream:streamid(), cowboy_req:req(), cowboy:opts()) -&amp;gt; boolean()) }  Configuration for the tracer stream handler.</description>
    </item>
    
    <item>
      <title>cowboy_websocket(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_websocket/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/cowboy_websocket/</guid>
      <description>Name cowboy_websocket - Websocket
Description The module cowboy_websocket implements Websocket as a Ranch protocol. It also defines a callback interface for handling Websocket connections.
Callbacks Websocket handlers must implement the following callback interface:
init(Req, State) -&amp;gt; {cowboy_websocket, Req, State} | {cowboy_websocket, Req, State, Opts} websocket_init(State) -&amp;gt; CallResult %% optional websocket_handle(InFrame, State) -&amp;gt; CallResult websocket_info(Info, State) -&amp;gt; CallResult terminate(Reason, PartialReq, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() PartialReq :: map() State :: any() Opts :: cowboy_websocket:opts() InFrame :: {text | binary | ping | pong, binary()} OutFrame :: cow_ws:frame() %% see types below Info :: any() CallResult :: {ok, State} | {ok, State, hibernate} | {reply, OutFrame | [OutFrame], State} | {reply, OutFrame | [OutFrame], State, hibernate} | {stop, State} Reason :: normal | stop | timeout | remote | {remote, cow_ws:close_code(), binary()} | {error, badencoding | badframe | closed | atom()} | {crash, error | exit | throw, any()}  The init/2 callback is common to all handlers.</description>
    </item>
    
    <item>
      <title>cowboy_websocket(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_websocket/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/cowboy_websocket/</guid>
      <description>Name cowboy_websocket - Websocket
Description The module cowboy_websocket implements Websocket as a Ranch protocol. It also defines a callback interface for handling Websocket connections.
Callbacks Websocket handlers must implement the following callback interface:
init(Req, State) -&amp;gt; {cowboy_websocket, Req, State} | {cowboy_websocket, Req, State, Opts} websocket_init(State) -&amp;gt; CallResult %% optional websocket_handle(InFrame, State) -&amp;gt; CallResult websocket_info(Info, State) -&amp;gt; CallResult terminate(Reason, PartialReq, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() PartialReq :: map() State :: any() Opts :: cowboy_websocket:opts() InFrame :: {text | binary | ping | pong, binary()} OutFrame :: cow_ws:frame() %% see types below Info :: any() CallResult :: {ok, State} | {ok, State, hibernate} | {reply, OutFrame | [OutFrame], State} | {reply, OutFrame | [OutFrame], State, hibernate} | {stop, State} Reason :: normal | stop | timeout | remote | {remote, cow_ws:close_code(), binary()} | {error, badencoding | badframe | closed | atom()} | {crash, error | exit | throw, any()}  The init/2 callback is common to all handlers.</description>
    </item>
    
    <item>
      <title>cowboy_websocket(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_websocket/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_websocket/</guid>
      <description>Name cowboy_websocket - Websocket
Description The module cowboy_websocket implements Websocket as a Ranch protocol. It also defines a callback interface for handling Websocket connections.
Callbacks Websocket handlers must implement the following callback interface:
init(Req, State) -&amp;gt; {cowboy_websocket, Req, State} | {cowboy_websocket, Req, State, Opts} websocket_init(State) -&amp;gt; CallResult %% optional websocket_handle(InFrame, State) -&amp;gt; CallResult websocket_info(Info, State) -&amp;gt; CallResult terminate(Reason, PartialReq, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() PartialReq :: map() State :: any() Opts :: cowboy_websocket:opts() InFrame :: {text | binary | ping | pong, binary()} OutFrame :: cow_ws:frame() %% see types below Info :: any() CallResult :: {ok, State} | {ok, State, hibernate} | {reply, OutFrame | [OutFrame], State} | {reply, OutFrame | [OutFrame], State, hibernate} | {stop, State} Reason :: normal | stop | timeout | remote | {remote, cow_ws:close_code(), binary()} | {error, badencoding | badframe | closed | atom()} | {crash, error | exit | throw, any()}  The init/2 callback is common to all handlers.</description>
    </item>
    
    <item>
      <title>cowboy_websocket(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_websocket/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_websocket/</guid>
      <description>Name cowboy_websocket - Websocket
Description The module cowboy_websocket implements Websocket as a Ranch protocol. It also defines a callback interface for handling Websocket connections.
Callbacks Websocket handlers must implement the following callback interface:
init(Req, State) -&amp;gt; {cowboy_websocket, Req, State} | {cowboy_websocket, Req, State, Opts} websocket_init(State) -&amp;gt; CallResult %% optional websocket_handle(InFrame, State) -&amp;gt; CallResult websocket_info(Info, State) -&amp;gt; CallResult terminate(Reason, PartialReq, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() PartialReq :: map() State :: any() Opts :: cowboy_websocket:opts() InFrame :: ping | pong | {text | binary | ping | pong, binary()} OutFrame :: cow_ws:frame() %% see types below Info :: any() CallResult :: {ok, State} | {ok, State, hibernate} | {reply, OutFrame | [OutFrame], State} | {reply, OutFrame | [OutFrame], State, hibernate} | {stop, State} Reason :: normal | stop | timeout | remote | {remote, cow_ws:close_code(), binary()} | {error, badencoding | badframe | closed | atom()} | {crash, error | exit | throw, any()}  The init/2 callback is common to all handlers.</description>
    </item>
    
    <item>
      <title>cowboy_websocket(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_websocket/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/cowboy_websocket/</guid>
      <description>Name cowboy_websocket - Websocket
Description The module cowboy_websocket implements Websocket as a Ranch protocol. It also defines a callback interface for handling Websocket connections.
Callbacks Websocket handlers must implement the following callback interface:
init(Req, State) -&amp;gt; {cowboy_websocket, Req, State} | {cowboy_websocket, Req, State, Opts} websocket_init(State) -&amp;gt; CallResult %% optional websocket_handle(InFrame, State) -&amp;gt; CallResult websocket_info(Info, State) -&amp;gt; CallResult terminate(Reason, PartialReq, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() PartialReq :: map() State :: any() Opts :: cowboy_websocket:opts() InFrame :: ping | pong | {text | binary | ping | pong, binary()} OutFrame :: cow_ws:frame() %% see types below Info :: any() CallResult :: {ok, State} | {ok, State, hibernate} | {reply, OutFrame | [OutFrame], State} | {reply, OutFrame | [OutFrame], State, hibernate} | {stop, State} Reason :: normal | stop | timeout | remote | {remote, cow_ws:close_code(), binary()} | {error, badencoding | badframe | closed | atom()} | {crash, error | exit | throw, any()}  The init/2 callback is common to all handlers.</description>
    </item>
    
    <item>
      <title>cowboy_websocket(3)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_websocket/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_websocket/</guid>
      <description>Name cowboy_websocket - Websocket
Description The module cowboy_websocket implements Websocket as a Ranch protocol. It also defines a callback interface for handling Websocket connections.
Callbacks Websocket handlers must implement the following callback interface:
init(Req, State) -&amp;gt; {cowboy_websocket, Req, State} | {cowboy_websocket, Req, State, Opts} websocket_init(State) -&amp;gt; CallResult %% optional websocket_handle(InFrame, State) -&amp;gt; CallResult websocket_info(Info, State) -&amp;gt; CallResult terminate(Reason, PartialReq, State) -&amp;gt; ok %% optional Req :: cowboy_req:req() PartialReq :: map() State :: any() Opts :: cowboy_websocket:opts() InFrame :: ping | pong | {text | binary | ping | pong, binary()} Info :: any() CallResult :: {commands(), State} | {commands(), State, hibernate} | Deprecated Deprecated :: {ok, State} | {ok, State, hibernate} | {reply, OutFrame | [OutFrame], State} | {reply, OutFrame | [OutFrame], State, hibernate} | {stop, State} OutFrame :: cow_ws:frame() %% see types below Reason :: normal | stop | timeout | remote | {remote, cow_ws:close_code(), binary()} | {error, badencoding | badframe | closed | atom()} | {crash, error | exit | throw, any()}  The init/2 callback is common to all handlers.</description>
    </item>
    
    <item>
      <title>Cowlib Function Reference</title>
      <link>https://ninenines.eu/docs/en/cowlib/2.8/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowlib/2.8/manual/</guid>
      <description>Name cowlib - Support library for manipulating Web protocols
Description Cowlib provides libraries for parsing and building messages for various Web protocols, including HTTP/1.1, HTTP/2 and Websocket.
It is optimized for completeness rather than speed. No value is ignored, they are all returned.
Modules cow_cookie(3) - Cookies   Dependencies crypto - Crypto functions   All these applications must be started before the cowlib application. To start Cowlib and all dependencies at once:</description>
    </item>
    
    <item>
      <title>cowlib(7)</title>
      <link>https://ninenines.eu/docs/en/cowlib/2.8/manual/cowlib_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowlib/2.8/manual/cowlib_app/</guid>
      <description>Name cowlib - Support library for manipulating Web protocols
Description Cowlib provides libraries for parsing and building messages for various Web protocols, including HTTP/1.1, HTTP/2 and Websocket.
It is optimized for completeness rather than speed. No value is ignored, they are all returned.
Modules cow_cookie(3) - Cookies   Dependencies crypto - Crypto functions   All these applications must be started before the cowlib application. To start Cowlib and all dependencies at once:</description>
    </item>
    
    <item>
      <title>Gun Function Reference</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/</guid>
      <description>Name gun - HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP
Description Gun is an HTTP client for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Gun aims to provide an easy to use, asynchronous and always-connected client. It maintains a permanent connection to the server and reconnects automatically when necessary.
Modules gun(3) - Asynchronous HTTP client   Dependencies cowlib(7) - Support library for manipulating Web protocols  ssl - Secure communication over sockets   All these applications must be started before the gun application.</description>
    </item>
    
    <item>
      <title>Gun Function Reference</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/</guid>
      <description>Name gun - HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP
Description Gun is an HTTP client for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Gun aims to provide an easy to use, asynchronous and always-connected client. It maintains a permanent connection to the server and reconnects automatically when necessary.
Modules gun(3) - Asynchronous HTTP client   Dependencies cowlib(7) - Support library for manipulating Web protocols  ssl - Secure communication over sockets   All these applications must be started before the gun application.</description>
    </item>
    
    <item>
      <title>Gun Function Reference</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/</guid>
      <description>Name gun - HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP
Description Gun is an HTTP client for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Gun aims to provide an easy to use, asynchronous and always-connected client. It maintains a permanent connection to the server and reconnects automatically when necessary.
Modules gun(3) - Asynchronous HTTP client   Dependencies cowlib(7) - Support library for manipulating Web protocols  ssl - Secure communication over sockets   All these applications must be started before the gun application.</description>
    </item>
    
    <item>
      <title>Gun Function Reference</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/</guid>
      <description>Name gun - HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP
Description Gun is an HTTP client for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Gun aims to provide an easy to use, asynchronous and always-connected client. It maintains a permanent connection to the server and reconnects automatically when necessary.
Modules gun(3) - Asynchronous HTTP client   Dependencies cowlib(7) - Support library for manipulating Web protocols  ssl - Secure communication over sockets   All these applications must be started before the gun application.</description>
    </item>
    
    <item>
      <title>Gun Function Reference</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/</guid>
      <description>Name gun - HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP
Description Gun is an HTTP client for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Gun aims to provide an easy to use, asynchronous and always-connected client. It maintains a permanent connection to the server and reconnects automatically when necessary.
Modules gun(3) - Asynchronous HTTP client   Dependencies cowlib(7) - Support library for manipulating Web protocols  ssl - Secure communication over sockets   All these applications must be started before the gun application.</description>
    </item>
    
    <item>
      <title>Gun User Guide</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/guide/</guid>
      <description>Introduction  Starting and stopping  Supported protocols  Connection  Using HTTP  Using Websocket   </description>
    </item>
    
    <item>
      <title>Gun User Guide</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/guide/</guid>
      <description>Interface Introduction  Starting and stopping  Supported protocols  Connection  Using HTTP  Using Websocket   Additional information Migrating from Gun 1.0 to 1.1   </description>
    </item>
    
    <item>
      <title>Gun User Guide</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/guide/</guid>
      <description>Interface Introduction  Starting and stopping  Supported protocols  Connection  Using HTTP  Using Websocket   Additional information Migrating from Gun 1.1 to 1.2  Migrating from Gun 1.0 to 1.1   </description>
    </item>
    
    <item>
      <title>Gun User Guide</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/guide/</guid>
      <description>Interface Introduction  Starting and stopping  Supported protocols  Connection  Using HTTP  Using Websocket   Additional information Changes since Gun 1.3  Migrating from Gun 1.2 to 1.3  Migrating from Gun 1.1 to 1.2  Migrating from Gun 1.0 to 1.1   </description>
    </item>
    
    <item>
      <title>Gun User Guide</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/guide/</guid>
      <description>Interface Introduction  Starting and stopping  Supported protocols  Connection  Using HTTP  Using Websocket   Additional information Migrating from Gun 1.3 to 2.0  Migrating from Gun 1.2 to 1.3  Migrating from Gun 1.1 to 1.2  Migrating from Gun 1.0 to 1.1   </description>
    </item>
    
    <item>
      <title>gun(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun/</guid>
      <description>Name gun - Asynchronous HTTP client
Description The gun module provides an asynchronous interface for connecting and communicating with Web servers over HTTP, HTTP/2 or Websocket.
Exports Connection:
gun:open(3) - Open a connection to the given host and port  gun:open_unix(3) - Open a connection to the given Unix domain socket   gun:close(3) - Brutally close the connection  gun:info(3) - Obtain information about the connection   Requests:</description>
    </item>
    
    <item>
      <title>gun(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun/</guid>
      <description>Name gun - Asynchronous HTTP client
Description The gun module provides an asynchronous interface for connecting and communicating with Web servers over HTTP, HTTP/2 or Websocket.
Exports Connection:
gun:open(3) - Open a connection to the given host and port  gun:open_unix(3) - Open a connection to the given Unix domain socket   gun:close(3) - Brutally close the connection  gun:info(3) - Obtain information about the connection   Requests:</description>
    </item>
    
    <item>
      <title>gun(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun/</guid>
      <description>Name gun - Asynchronous HTTP client
Description The gun module provides an asynchronous interface for connecting and communicating with Web servers over HTTP, HTTP/2 or Websocket.
Exports Connection:
gun:open(3) - Open a connection to the given host and port  gun:open_unix(3) - Open a connection to the given Unix domain socket   gun:close(3) - Brutally close the connection  gun:info(3) - Obtain information about the connection   Requests:</description>
    </item>
    
    <item>
      <title>gun(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun/</guid>
      <description>Name gun - Asynchronous HTTP client
Description The gun module provides an asynchronous interface for connecting and communicating with Web servers over HTTP, HTTP/2 or Websocket.
Exports Connection:
gun:open(3) - Open a connection to the given host and port  gun:open_unix(3) - Open a connection to the given Unix domain socket   gun:close(3) - Brutally close the connection  gun:info(3) - Obtain information about the connection   Requests:</description>
    </item>
    
    <item>
      <title>gun(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun/</guid>
      <description>Name gun - Asynchronous HTTP client
Description The gun module provides an asynchronous interface for connecting and communicating with Web servers over HTTP, HTTP/2 or Websocket.
Exports Connection:
gun:open(3) - Open a connection to the given host and port  gun:open_unix(3) - Open a connection to the given Unix domain socket  gun:set_owner(3) - Set a new owner for the connection  gun:shutdown(3) - Gracefully close the connection  gun:close(3) - Brutally close the connection  gun:info(3) - Obtain information about the connection   Requests:</description>
    </item>
    
    <item>
      <title>gun(7)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun_app/</guid>
      <description>Name gun - HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP
Description Gun is an HTTP client for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Gun aims to provide an easy to use, asynchronous and always-connected client. It maintains a permanent connection to the server and reconnects automatically when necessary.
Modules gun(3) - Asynchronous HTTP client   Dependencies cowlib(7) - Support library for manipulating Web protocols  ssl - Secure communication over sockets   All these applications must be started before the gun application.</description>
    </item>
    
    <item>
      <title>gun(7)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun_app/</guid>
      <description>Name gun - HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP
Description Gun is an HTTP client for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Gun aims to provide an easy to use, asynchronous and always-connected client. It maintains a permanent connection to the server and reconnects automatically when necessary.
Modules gun(3) - Asynchronous HTTP client   Dependencies cowlib(7) - Support library for manipulating Web protocols  ssl - Secure communication over sockets   All these applications must be started before the gun application.</description>
    </item>
    
    <item>
      <title>gun(7)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun_app/</guid>
      <description>Name gun - HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP
Description Gun is an HTTP client for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Gun aims to provide an easy to use, asynchronous and always-connected client. It maintains a permanent connection to the server and reconnects automatically when necessary.
Modules gun(3) - Asynchronous HTTP client   Dependencies cowlib(7) - Support library for manipulating Web protocols  ssl - Secure communication over sockets   All these applications must be started before the gun application.</description>
    </item>
    
    <item>
      <title>gun(7)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun_app/</guid>
      <description>Name gun - HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP
Description Gun is an HTTP client for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Gun aims to provide an easy to use, asynchronous and always-connected client. It maintains a permanent connection to the server and reconnects automatically when necessary.
Modules gun(3) - Asynchronous HTTP client   Dependencies cowlib(7) - Support library for manipulating Web protocols  ssl - Secure communication over sockets   All these applications must be started before the gun application.</description>
    </item>
    
    <item>
      <title>gun(7)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun_app/</guid>
      <description>Name gun - HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP
Description Gun is an HTTP client for Erlang/OTP with support for the HTTP/1.1, HTTP/2 and Websocket protocols.
Gun aims to provide an easy to use, asynchronous and always-connected client. It maintains a permanent connection to the server and reconnects automatically when necessary.
Modules gun(3) - Asynchronous HTTP client   Dependencies cowlib(7) - Support library for manipulating Web protocols  ssl - Secure communication over sockets   All these applications must be started before the gun application.</description>
    </item>
    
    <item>
      <title>gun:await(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.await/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.await/</guid>
      <description>Name gun:await - Wait for a response
Description await(ConnPid, StreamRef) -&amp;gt; await(ConnPid, StreamRef, 5000, MonitorRef) await(ConnPid, StreamRef, MonitorRef) -&amp;gt; await(ConnPid, StreamRef, 5000, MonitorRef) await(ConnPid, StreamRef, Timeout) -&amp;gt; await(ConnPid, StreamRef, Timeout, MonitorRef) await(ConnPid, StreamRef, Timeout, MonitorRef) -&amp;gt; Result ConnPid :: pid() StreamRef :: reference() MonitorRef :: reference() Timeout :: timeout() Result :: tuple() - see below  Wait for a response.
This function waits for a message from the given stream and returns it as a tuple.</description>
    </item>
    
    <item>
      <title>gun:await(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.await/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.await/</guid>
      <description>Name gun:await - Wait for a response
Description await(ConnPid, StreamRef) -&amp;gt; await(ConnPid, StreamRef, 5000, MonitorRef) await(ConnPid, StreamRef, MonitorRef) -&amp;gt; await(ConnPid, StreamRef, 5000, MonitorRef) await(ConnPid, StreamRef, Timeout) -&amp;gt; await(ConnPid, StreamRef, Timeout, MonitorRef) await(ConnPid, StreamRef, Timeout, MonitorRef) -&amp;gt; Result ConnPid :: pid() StreamRef :: reference() MonitorRef :: reference() Timeout :: timeout() Result :: tuple() - see below  Wait for a response.
This function waits for a message from the given stream and returns it as a tuple.</description>
    </item>
    
    <item>
      <title>gun:await(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.await/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.await/</guid>
      <description>Name gun:await - Wait for a response
Description await(ConnPid, StreamRef) -&amp;gt; await(ConnPid, StreamRef, 5000, MonitorRef) await(ConnPid, StreamRef, MonitorRef) -&amp;gt; await(ConnPid, StreamRef, 5000, MonitorRef) await(ConnPid, StreamRef, Timeout) -&amp;gt; await(ConnPid, StreamRef, Timeout, MonitorRef) await(ConnPid, StreamRef, Timeout, MonitorRef) -&amp;gt; Result ConnPid :: pid() StreamRef :: reference() MonitorRef :: reference() Timeout :: timeout() Result :: tuple() - see below  Wait for a response.
This function waits for a message from the given stream and returns it as a tuple.</description>
    </item>
    
    <item>
      <title>gun:await(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.await/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.await/</guid>
      <description>Name gun:await - Wait for a response
Description await(ConnPid, StreamRef) -&amp;gt; await(ConnPid, StreamRef, 5000, MonitorRef) await(ConnPid, StreamRef, MonitorRef) -&amp;gt; await(ConnPid, StreamRef, 5000, MonitorRef) await(ConnPid, StreamRef, Timeout) -&amp;gt; await(ConnPid, StreamRef, Timeout, MonitorRef) await(ConnPid, StreamRef, Timeout, MonitorRef) -&amp;gt; Result ConnPid :: pid() StreamRef :: reference() MonitorRef :: reference() Timeout :: timeout() Result :: tuple() - see below  Wait for a response.
This function waits for a message from the given stream and returns it as a tuple.</description>
    </item>
    
    <item>
      <title>gun:await(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.await/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.await/</guid>
      <description>Name gun:await - Wait for a response
Description await(ConnPid, StreamRef) -&amp;gt; await(ConnPid, StreamRef, 5000, MonitorRef) await(ConnPid, StreamRef, MonitorRef) -&amp;gt; await(ConnPid, StreamRef, 5000, MonitorRef) await(ConnPid, StreamRef, Timeout) -&amp;gt; await(ConnPid, StreamRef, Timeout, MonitorRef) await(ConnPid, StreamRef, Timeout, MonitorRef) -&amp;gt; Result ConnPid :: pid() StreamRef :: reference() MonitorRef :: reference() Timeout :: timeout() Result :: tuple() - see below  Wait for a response.
This function waits for a message from the given stream and returns it as a tuple.</description>
    </item>
    
    <item>
      <title>gun:await_body(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.await_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.await_body/</guid>
      <description>Name gun:await_body - Wait for the complete response body
Description await_body(ConnPid, StreamRef) -&amp;gt; await_body(ConnPid, StreamRef, 5000, MonitorRef) await_body(ConnPid, StreamRef, MonitorRef) -&amp;gt; await_body(ConnPid, StreamRef, 5000, MonitorRef) await_body(ConnPid, StreamRef, Timeout) -&amp;gt; await_body(ConnPid, StreamRef, Timeout, MonitorRef) await_body(ConnPid, StreamRef, Timeout, MonitorRef) -&amp;gt; {ok, Body} | {ok, Body, Trailers} | {error, Reason} ConnPid :: pid() StreamRef :: reference() MonitorRef :: reference() Timeout :: timeout() Body :: binary() Trailers :: [{binary(), binary()}] Reason :: timeout | any()  Wait for the complete response body.</description>
    </item>
    
    <item>
      <title>gun:await_body(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.await_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.await_body/</guid>
      <description>Name gun:await_body - Wait for the complete response body
Description await_body(ConnPid, StreamRef) -&amp;gt; await_body(ConnPid, StreamRef, 5000, MonitorRef) await_body(ConnPid, StreamRef, MonitorRef) -&amp;gt; await_body(ConnPid, StreamRef, 5000, MonitorRef) await_body(ConnPid, StreamRef, Timeout) -&amp;gt; await_body(ConnPid, StreamRef, Timeout, MonitorRef) await_body(ConnPid, StreamRef, Timeout, MonitorRef) -&amp;gt; {ok, Body} | {ok, Body, Trailers} | {error, Reason} ConnPid :: pid() StreamRef :: reference() MonitorRef :: reference() Timeout :: timeout() Body :: binary() Trailers :: [{binary(), binary()}] Reason :: timeout | any()  Wait for the complete response body.</description>
    </item>
    
    <item>
      <title>gun:await_body(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.await_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.await_body/</guid>
      <description>Name gun:await_body - Wait for the complete response body
Description await_body(ConnPid, StreamRef) -&amp;gt; await_body(ConnPid, StreamRef, 5000, MonitorRef) await_body(ConnPid, StreamRef, MonitorRef) -&amp;gt; await_body(ConnPid, StreamRef, 5000, MonitorRef) await_body(ConnPid, StreamRef, Timeout) -&amp;gt; await_body(ConnPid, StreamRef, Timeout, MonitorRef) await_body(ConnPid, StreamRef, Timeout, MonitorRef) -&amp;gt; {ok, Body} | {ok, Body, Trailers} | {error, Reason} ConnPid :: pid() StreamRef :: reference() MonitorRef :: reference() Timeout :: timeout() Body :: binary() Trailers :: [{binary(), binary()}] Reason :: timeout | any()  Wait for the complete response body.</description>
    </item>
    
    <item>
      <title>gun:await_body(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.await_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.await_body/</guid>
      <description>Name gun:await_body - Wait for the complete response body
Description await_body(ConnPid, StreamRef) -&amp;gt; await_body(ConnPid, StreamRef, 5000, MonitorRef) await_body(ConnPid, StreamRef, MonitorRef) -&amp;gt; await_body(ConnPid, StreamRef, 5000, MonitorRef) await_body(ConnPid, StreamRef, Timeout) -&amp;gt; await_body(ConnPid, StreamRef, Timeout, MonitorRef) await_body(ConnPid, StreamRef, Timeout, MonitorRef) -&amp;gt; {ok, Body} | {ok, Body, Trailers} | {error, Reason} ConnPid :: pid() StreamRef :: reference() MonitorRef :: reference() Timeout :: timeout() Body :: binary() Trailers :: [{binary(), binary()}] Reason :: timeout | any()  Wait for the complete response body.</description>
    </item>
    
    <item>
      <title>gun:await_body(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.await_body/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.await_body/</guid>
      <description>Name gun:await_body - Wait for the complete response body
Description await_body(ConnPid, StreamRef) -&amp;gt; await_body(ConnPid, StreamRef, 5000, MonitorRef) await_body(ConnPid, StreamRef, MonitorRef) -&amp;gt; await_body(ConnPid, StreamRef, 5000, MonitorRef) await_body(ConnPid, StreamRef, Timeout) -&amp;gt; await_body(ConnPid, StreamRef, Timeout, MonitorRef) await_body(ConnPid, StreamRef, Timeout, MonitorRef) -&amp;gt; {ok, Body} | {ok, Body, Trailers} | {error, Reason} ConnPid :: pid() StreamRef :: reference() MonitorRef :: reference() Timeout :: timeout() Body :: binary() Trailers :: [{binary(), binary()}] Reason :: {stream_error | connection_error | down, any()} | timeout  Wait for the complete response body.</description>
    </item>
    
    <item>
      <title>gun:await_up(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.await_up/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.await_up/</guid>
      <description>Name gun:await_up - Wait for the connection to be up
Description await_up(ConnPid) -&amp;gt; await_up(ConnPid, 5000, MonitorRef) await_up(ConnPid, MonitorRef) -&amp;gt; await_up(ConnPid, 5000, MonitorRef) await_up(ConnPid, Timeout) -&amp;gt; await_up(ConnPid, Timeout, MonitorRef) await_up(ConnPid, Timeout, MonitorRef) -&amp;gt; {ok, Protocol} | {error, Reason} ConnPid :: pid() MonitorRef :: reference() Timeout :: timeout() Protocol :: http | http2 Reason :: timeout | any()  Wait for the connection to be up.
Arguments ConnPid The pid of the Gun connection process.</description>
    </item>
    
    <item>
      <title>gun:await_up(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.await_up/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.await_up/</guid>
      <description>Name gun:await_up - Wait for the connection to be up
Description await_up(ConnPid) -&amp;gt; await_up(ConnPid, 5000, MonitorRef) await_up(ConnPid, MonitorRef) -&amp;gt; await_up(ConnPid, 5000, MonitorRef) await_up(ConnPid, Timeout) -&amp;gt; await_up(ConnPid, Timeout, MonitorRef) await_up(ConnPid, Timeout, MonitorRef) -&amp;gt; {ok, Protocol} | {error, Reason} ConnPid :: pid() MonitorRef :: reference() Timeout :: timeout() Protocol :: http | http2 Reason :: timeout | any()  Wait for the connection to be up.
Arguments ConnPid The pid of the Gun connection process.</description>
    </item>
    
    <item>
      <title>gun:await_up(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.await_up/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.await_up/</guid>
      <description>Name gun:await_up - Wait for the connection to be up
Description await_up(ConnPid) -&amp;gt; await_up(ConnPid, 5000, MonitorRef) await_up(ConnPid, MonitorRef) -&amp;gt; await_up(ConnPid, 5000, MonitorRef) await_up(ConnPid, Timeout) -&amp;gt; await_up(ConnPid, Timeout, MonitorRef) await_up(ConnPid, Timeout, MonitorRef) -&amp;gt; {ok, Protocol} | {error, Reason} ConnPid :: pid() MonitorRef :: reference() Timeout :: timeout() Protocol :: http | http2 Reason :: timeout | any()  Wait for the connection to be up.
Arguments ConnPid The pid of the Gun connection process.</description>
    </item>
    
    <item>
      <title>gun:await_up(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.await_up/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.await_up/</guid>
      <description>Name gun:await_up - Wait for the connection to be up
Description await_up(ConnPid) -&amp;gt; await_up(ConnPid, 5000, MonitorRef) await_up(ConnPid, MonitorRef) -&amp;gt; await_up(ConnPid, 5000, MonitorRef) await_up(ConnPid, Timeout) -&amp;gt; await_up(ConnPid, Timeout, MonitorRef) await_up(ConnPid, Timeout, MonitorRef) -&amp;gt; {ok, Protocol} | {error, Reason} ConnPid :: pid() MonitorRef :: reference() Timeout :: timeout() Protocol :: http | http2 Reason :: timeout | any()  Wait for the connection to be up.
Arguments ConnPid The pid of the Gun connection process.</description>
    </item>
    
    <item>
      <title>gun:await_up(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.await_up/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.await_up/</guid>
      <description>Name gun:await_up - Wait for the connection to be up
Description await_up(ConnPid) -&amp;gt; await_up(ConnPid, 5000, MonitorRef) await_up(ConnPid, MonitorRef) -&amp;gt; await_up(ConnPid, 5000, MonitorRef) await_up(ConnPid, Timeout) -&amp;gt; await_up(ConnPid, Timeout, MonitorRef) await_up(ConnPid, Timeout, MonitorRef) -&amp;gt; {ok, Protocol} | {error, Reason} ConnPid :: pid() MonitorRef :: reference() Timeout :: timeout() Protocol :: http | http2 | socks Reason :: {down, any()} | timeout  Wait for the connection to be up.
Arguments ConnPid The pid of the Gun connection process.</description>
    </item>
    
    <item>
      <title>gun:cancel(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.cancel/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.cancel/</guid>
      <description>Name gun:cancel - Cancel the given stream
Description cancel(ConnPid, StreamRef) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference()  Cancel the given stream.
The behavior of this function depends on the protocol selected.
HTTP/1.1 does not support this feature. Gun will simply silence the stream and stop relaying messages. Gun may also decide to close the connection if the response body is too large, to avoid wasting time and bandwidth.</description>
    </item>
    
    <item>
      <title>gun:cancel(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.cancel/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.cancel/</guid>
      <description>Name gun:cancel - Cancel the given stream
Description cancel(ConnPid, StreamRef) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference()  Cancel the given stream.
The behavior of this function depends on the protocol selected.
HTTP/1.1 does not support this feature. Gun will simply silence the stream and stop relaying messages. Gun may also decide to close the connection if the response body is too large, to avoid wasting time and bandwidth.</description>
    </item>
    
    <item>
      <title>gun:cancel(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.cancel/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.cancel/</guid>
      <description>Name gun:cancel - Cancel the given stream
Description cancel(ConnPid, StreamRef) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference()  Cancel the given stream.
The behavior of this function depends on the protocol selected.
HTTP/1.1 does not support this feature. Gun will simply silence the stream and stop relaying messages. Gun may also decide to close the connection if the response body is too large, to avoid wasting time and bandwidth.</description>
    </item>
    
    <item>
      <title>gun:cancel(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.cancel/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.cancel/</guid>
      <description>Name gun:cancel - Cancel the given stream
Description cancel(ConnPid, StreamRef) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference()  Cancel the given stream.
The behavior of this function depends on the protocol selected.
HTTP/1.1 does not support this feature. Gun will simply silence the stream and stop relaying messages. Gun may also decide to close the connection if the response body is too large, to avoid wasting time and bandwidth.</description>
    </item>
    
    <item>
      <title>gun:cancel(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.cancel/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.cancel/</guid>
      <description>Name gun:cancel - Cancel the given stream
Description cancel(ConnPid, StreamRef) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference()  Cancel the given stream.
The behavior of this function depends on the protocol selected.
HTTP/1.1 does not support this feature. Gun will simply silence the stream and stop relaying messages. Gun may also decide to close the connection if the response body is too large, to avoid wasting time and bandwidth.</description>
    </item>
    
    <item>
      <title>gun:close(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.close/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.close/</guid>
      <description>Name gun:close - Brutally close the connection
Description close(ConnPid) -&amp;gt; ok ConnPid :: pid()  Brutally close the connection.
Arguments ConnPid The pid of the Gun connection process.
  Return value The atom ok is returned.
Changelog 1.0: Function introduced.   Examples Close the connection ok = gun:close(ConnPid).  See also gun(3), gun:open(3), gun:open_unix(3)</description>
    </item>
    
    <item>
      <title>gun:close(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.close/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.close/</guid>
      <description>Name gun:close - Brutally close the connection
Description close(ConnPid) -&amp;gt; ok ConnPid :: pid()  Brutally close the connection.
Arguments ConnPid The pid of the Gun connection process.
  Return value The atom ok is returned.
Changelog 1.0: Function introduced.   Examples Close the connection ok = gun:close(ConnPid).  See also gun(3), gun:open(3), gun:open_unix(3)</description>
    </item>
    
    <item>
      <title>gun:close(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.close/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.close/</guid>
      <description>Name gun:close - Brutally close the connection
Description close(ConnPid) -&amp;gt; ok ConnPid :: pid()  Brutally close the connection.
Arguments ConnPid The pid of the Gun connection process.
  Return value The atom ok is returned.
Changelog 1.0: Function introduced.   Examples Close the connection ok = gun:close(ConnPid).  See also gun(3), gun:open(3), gun:open_unix(3)</description>
    </item>
    
    <item>
      <title>gun:close(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.close/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.close/</guid>
      <description>Name gun:close - Brutally close the connection
Description close(ConnPid) -&amp;gt; ok ConnPid :: pid()  Brutally close the connection.
Arguments ConnPid The pid of the Gun connection process.
  Return value The atom ok is returned.
Changelog 1.0: Function introduced.   Examples Close the connection ok = gun:close(ConnPid).  See also gun(3), gun:open(3), gun:open_unix(3)</description>
    </item>
    
    <item>
      <title>gun:close(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.close/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.close/</guid>
      <description>Name gun:close - Brutally close the connection
Description close(ConnPid) -&amp;gt; ok ConnPid :: pid()  Brutally close the connection.
Arguments ConnPid The pid of the Gun connection process.
  Return value The atom ok is returned.
Changelog 1.0: Function introduced.   Examples Close the connection ok = gun:close(ConnPid).  See also gun(3), gun:open(3), gun:open_unix(3), gun:shutdown(3)</description>
    </item>
    
    <item>
      <title>gun:connect(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.connect/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.connect/</guid>
      <description>Name gun:connect - Establish a tunnel to the origin server
Description connect(ConnPid, Destination) -&amp;gt; connect(ConnPid, Destination, [], #{}). connect(ConnPid, Destination, Headers) -&amp;gt; connect(ConnPid, Destination, Headers, #{}). connect(ConnPid, Destination, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Destination :: gun:connect_destination() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Establish a tunnel to the origin server.
This feature is currently only available for HTTP/1.1 connections. Upon successful completion of the CONNECT request a tunnel is established and subsequent requests will go through the tunnel.</description>
    </item>
    
    <item>
      <title>gun:connect(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.connect/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.connect/</guid>
      <description>Name gun:connect - Establish a tunnel to the origin server
Description connect(ConnPid, Destination) -&amp;gt; connect(ConnPid, Destination, [], #{}). connect(ConnPid, Destination, Headers) -&amp;gt; connect(ConnPid, Destination, Headers, #{}). connect(ConnPid, Destination, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Destination :: gun:connect_destination() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Establish a tunnel to the origin server.
This feature is currently only available for HTTP/1.1 connections. Upon successful completion of the CONNECT request a tunnel is established and subsequent requests will go through the tunnel.</description>
    </item>
    
    <item>
      <title>gun:connect(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.connect/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.connect/</guid>
      <description>Name gun:connect - Establish a tunnel to the origin server
Description connect(ConnPid, Destination) -&amp;gt; connect(ConnPid, Destination, [], #{}). connect(ConnPid, Destination, Headers) -&amp;gt; connect(ConnPid, Destination, Headers, #{}). connect(ConnPid, Destination, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Destination :: gun:connect_destination() Headers :: gun:req_headers() ReqOpts :: gun:req_opts() StreamRef :: reference()  Establish a tunnel to the origin server.
This feature is currently only available for HTTP/1.1 connections. Upon successful completion of the CONNECT request a tunnel is established and subsequent requests will go through the tunnel.</description>
    </item>
    
    <item>
      <title>gun:data(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.data/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.data/</guid>
      <description>Name gun:data - Stream the body of a request
Description data(ConnPid, StreamRef, IsFin, Data) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Data :: iodata()  Stream the body of a request.
This function can only be used if the original request had headers indicating that a body would be streamed.
All calls to this function must use the nofin flag except for the last which must use fin to indicate the end of the request body.</description>
    </item>
    
    <item>
      <title>gun:data(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.data/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.data/</guid>
      <description>Name gun:data - Stream the body of a request
Description data(ConnPid, StreamRef, IsFin, Data) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Data :: iodata()  Stream the body of a request.
This function can only be used if the original request had headers indicating that a body would be streamed.
All calls to this function must use the nofin flag except for the last which must use fin to indicate the end of the request body.</description>
    </item>
    
    <item>
      <title>gun:data(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.data/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.data/</guid>
      <description>Name gun:data - Stream the body of a request
Description data(ConnPid, StreamRef, IsFin, Data) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Data :: iodata()  Stream the body of a request.
This function can only be used if the original request had headers indicating that a body would be streamed.
All calls to this function must use the nofin flag except for the last which must use fin to indicate the end of the request body.</description>
    </item>
    
    <item>
      <title>gun:data(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.data/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.data/</guid>
      <description>Name gun:data - Stream the body of a request
Description data(ConnPid, StreamRef, IsFin, Data) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Data :: iodata()  Stream the body of a request.
This function can only be used if the original request had headers indicating that a body would be streamed.
All calls to this function must use the nofin flag except for the last which must use fin to indicate the end of the request body.</description>
    </item>
    
    <item>
      <title>gun:data(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.data/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.data/</guid>
      <description>Name gun:data - Stream the body of a request
Description data(ConnPid, StreamRef, IsFin, Data) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Data :: iodata()  Stream the body of a request.
This function can only be used if the original request had headers indicating that a body would be streamed.
All calls to this function must use the nofin flag except for the last which must use fin to indicate the end of the request body.</description>
    </item>
    
    <item>
      <title>gun:delete(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.delete/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.delete/</guid>
      <description>Name gun:delete - Delete a resource
Description delete(ConnPid, Path) -&amp;gt; delete(ConnPid, Path, [], #{}). delete(ConnPid, Path, Headers) -&amp;gt; delete(ConnPid, Path, Headers, #{}) delete(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Delete a resource.
Arguments ConnPid The pid of the Gun connection process.
 Path Path to the resource.
 Headers Additional request headers.
 ReqOpts Request options.</description>
    </item>
    
    <item>
      <title>gun:delete(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.delete/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.delete/</guid>
      <description>Name gun:delete - Delete a resource
Description delete(ConnPid, Path) -&amp;gt; delete(ConnPid, Path, [], #{}). delete(ConnPid, Path, Headers) -&amp;gt; delete(ConnPid, Path, Headers, #{}) delete(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Delete a resource.
Arguments ConnPid The pid of the Gun connection process.
 Path Path to the resource.
 Headers Additional request headers.
 ReqOpts Request options.</description>
    </item>
    
    <item>
      <title>gun:delete(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.delete/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.delete/</guid>
      <description>Name gun:delete - Delete a resource
Description delete(ConnPid, Path) -&amp;gt; delete(ConnPid, Path, [], #{}). delete(ConnPid, Path, Headers) -&amp;gt; delete(ConnPid, Path, Headers, #{}) delete(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Delete a resource.
Arguments ConnPid The pid of the Gun connection process.
 Path Path to the resource.
 Headers Additional request headers.
 ReqOpts Request options.</description>
    </item>
    
    <item>
      <title>gun:delete(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.delete/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.delete/</guid>
      <description>Name gun:delete - Delete a resource
Description delete(ConnPid, Path) -&amp;gt; delete(ConnPid, Path, [], #{}). delete(ConnPid, Path, Headers) -&amp;gt; delete(ConnPid, Path, Headers, #{}) delete(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Delete a resource.
Arguments ConnPid The pid of the Gun connection process.
 Path Path to the resource.
 Headers Additional request headers.
 ReqOpts Request options.</description>
    </item>
    
    <item>
      <title>gun:delete(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.delete/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.delete/</guid>
      <description>Name gun:delete - Delete a resource
Description delete(ConnPid, Path) -&amp;gt; delete(ConnPid, Path, [], #{}). delete(ConnPid, Path, Headers) -&amp;gt; delete(ConnPid, Path, Headers, #{}) delete(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() ReqOpts :: gun:req_opts() StreamRef :: reference()  Delete a resource.
Arguments ConnPid The pid of the Gun connection process.
 Path Path to the resource.
 Headers Additional request headers.
 ReqOpts Request options.</description>
    </item>
    
    <item>
      <title>gun:flush(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.flush/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.flush/</guid>
      <description>Name gun:flush - Flush all messages related to a connection or a stream
Description flush(ConnPid) -&amp;gt; ok flush(StreamRef) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference()  Flush all messages related to a connection or a stream.
Arguments Either of these arguments may be provided:
ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
  Return value The atom ok is returned.</description>
    </item>
    
    <item>
      <title>gun:flush(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.flush/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.flush/</guid>
      <description>Name gun:flush - Flush all messages related to a connection or a stream
Description flush(ConnPid) -&amp;gt; ok flush(StreamRef) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference()  Flush all messages related to a connection or a stream.
Arguments Either of these arguments may be provided:
ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
  Return value The atom ok is returned.</description>
    </item>
    
    <item>
      <title>gun:flush(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.flush/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.flush/</guid>
      <description>Name gun:flush - Flush all messages related to a connection or a stream
Description flush(ConnPid) -&amp;gt; ok flush(StreamRef) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference()  Flush all messages related to a connection or a stream.
Arguments Either of these arguments may be provided:
ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
  Return value The atom ok is returned.</description>
    </item>
    
    <item>
      <title>gun:flush(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.flush/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.flush/</guid>
      <description>Name gun:flush - Flush all messages related to a connection or a stream
Description flush(ConnPid) -&amp;gt; ok flush(StreamRef) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference()  Flush all messages related to a connection or a stream.
Arguments Either of these arguments may be provided:
ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
  Return value The atom ok is returned.</description>
    </item>
    
    <item>
      <title>gun:flush(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.flush/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.flush/</guid>
      <description>Name gun:flush - Flush all messages related to a connection or a stream
Description flush(ConnPid) -&amp;gt; ok flush(StreamRef) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference()  Flush all messages related to a connection or a stream.
Arguments Either of these arguments may be provided:
ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
  Return value The atom ok is returned.</description>
    </item>
    
    <item>
      <title>gun:get(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.get/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.get/</guid>
      <description>Name gun:get - Get a resource representation
Description get(ConnPid, Path) -&amp;gt; get(ConnPid, Path, [], #{}). get(ConnPid, Path, Headers) -&amp;gt; get(ConnPid, Path, Headers, #{}) get(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Get a resource representation.
Arguments ConnPid The pid of the Gun connection process.
 Path Path to the resource.
 Headers Additional request headers.</description>
    </item>
    
    <item>
      <title>gun:get(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.get/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.get/</guid>
      <description>Name gun:get - Get a resource representation
Description get(ConnPid, Path) -&amp;gt; get(ConnPid, Path, [], #{}). get(ConnPid, Path, Headers) -&amp;gt; get(ConnPid, Path, Headers, #{}) get(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Get a resource representation.
Arguments ConnPid The pid of the Gun connection process.
 Path Path to the resource.
 Headers Additional request headers.</description>
    </item>
    
    <item>
      <title>gun:get(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.get/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.get/</guid>
      <description>Name gun:get - Get a resource representation
Description get(ConnPid, Path) -&amp;gt; get(ConnPid, Path, [], #{}). get(ConnPid, Path, Headers) -&amp;gt; get(ConnPid, Path, Headers, #{}) get(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Get a resource representation.
Arguments ConnPid The pid of the Gun connection process.
 Path Path to the resource.
 Headers Additional request headers.</description>
    </item>
    
    <item>
      <title>gun:get(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.get/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.get/</guid>
      <description>Name gun:get - Get a resource representation
Description get(ConnPid, Path) -&amp;gt; get(ConnPid, Path, [], #{}). get(ConnPid, Path, Headers) -&amp;gt; get(ConnPid, Path, Headers, #{}) get(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Get a resource representation.
Arguments ConnPid The pid of the Gun connection process.
 Path Path to the resource.
 Headers Additional request headers.</description>
    </item>
    
    <item>
      <title>gun:get(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.get/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.get/</guid>
      <description>Name gun:get - Get a resource representation
Description get(ConnPid, Path) -&amp;gt; get(ConnPid, Path, [], #{}). get(ConnPid, Path, Headers) -&amp;gt; get(ConnPid, Path, Headers, #{}) get(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() ReqOpts :: gun:req_opts() StreamRef :: reference()  Get a resource representation.
Arguments ConnPid The pid of the Gun connection process.
 Path Path to the resource.
 Headers Additional request headers.
 ReqOpts Request options.</description>
    </item>
    
    <item>
      <title>gun:head(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.head/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.head/</guid>
      <description>Name gun:head - Get headers of a resource representation
Description head(ConnPid, Path) -&amp;gt; head(ConnPid, Path, [], #{}). head(ConnPid, Path, Headers) -&amp;gt; head(ConnPid, Path, Headers, #{}) head(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Get headers of a resource representation.
This function performs the same operation as gun:get(3), except the server will not send the resource representation, only the response&amp;apos;s status code and headers.</description>
    </item>
    
    <item>
      <title>gun:head(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.head/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.head/</guid>
      <description>Name gun:head - Get headers of a resource representation
Description head(ConnPid, Path) -&amp;gt; head(ConnPid, Path, [], #{}). head(ConnPid, Path, Headers) -&amp;gt; head(ConnPid, Path, Headers, #{}) head(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Get headers of a resource representation.
This function performs the same operation as gun:get(3), except the server will not send the resource representation, only the response&amp;apos;s status code and headers.</description>
    </item>
    
    <item>
      <title>gun:head(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.head/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.head/</guid>
      <description>Name gun:head - Get headers of a resource representation
Description head(ConnPid, Path) -&amp;gt; head(ConnPid, Path, [], #{}). head(ConnPid, Path, Headers) -&amp;gt; head(ConnPid, Path, Headers, #{}) head(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Get headers of a resource representation.
This function performs the same operation as gun:get(3), except the server will not send the resource representation, only the response&amp;apos;s status code and headers.</description>
    </item>
    
    <item>
      <title>gun:head(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.head/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.head/</guid>
      <description>Name gun:head - Get headers of a resource representation
Description head(ConnPid, Path) -&amp;gt; head(ConnPid, Path, [], #{}). head(ConnPid, Path, Headers) -&amp;gt; head(ConnPid, Path, Headers, #{}) head(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Get headers of a resource representation.
This function performs the same operation as gun:get(3), except the server will not send the resource representation, only the response&amp;apos;s status code and headers.</description>
    </item>
    
    <item>
      <title>gun:head(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.head/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.head/</guid>
      <description>Name gun:head - Get headers of a resource representation
Description head(ConnPid, Path) -&amp;gt; head(ConnPid, Path, [], #{}). head(ConnPid, Path, Headers) -&amp;gt; head(ConnPid, Path, Headers, #{}) head(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() ReqOpts :: gun:req_opts() StreamRef :: reference()  Get headers of a resource representation.
This function performs the same operation as gun:get(3), except the server will not send the resource representation, only the response&amp;apos;s status code and headers.</description>
    </item>
    
    <item>
      <title>gun:headers(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.headers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.headers/</guid>
      <description>Name gun:headers - Initiate the given request
Description headers(ConnPid, Method, Path, Headers) -&amp;gt; headers(ConnPid, Method, Path, Headers, #{}) headers(ConnPid, Method, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Method :: binary() Path :: iodata() Headers :: gun:req_headers() ReqOpts :: gun:req_opts() StreamRef :: reference()  Initiate the given request.
This is a general purpose function that should only be used when other method-specific functions do not apply.
The function headers/4,5 initiates a request but does not send the request body.</description>
    </item>
    
    <item>
      <title>gun:info(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.info/</guid>
      <description>Name gun:info - Obtain information about the connection
Description info(ConnPid) -&amp;gt; Info ConnPid :: pid() Info :: #{ sock_ip =&amp;gt; inet:ip_address(), sock_port =&amp;gt; inet:port_number() }  Obtain information about the connection.
Arguments ConnPid The pid of the Gun connection process.
  Return value A map is returned containing various informations about the connection.
Changelog 1.0: Function introduced.   Examples Obtain information about the connection Info = gun:info(ConnPid).  See also gun(3), gun:open(3), gun:open_unix(3)</description>
    </item>
    
    <item>
      <title>gun:info(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.info/</guid>
      <description>Name gun:info - Obtain information about the connection
Description info(ConnPid) -&amp;gt; Info ConnPid :: pid() Info :: #{ sock_ip =&amp;gt; inet:ip_address(), sock_port =&amp;gt; inet:port_number() }  Obtain information about the connection.
Arguments ConnPid The pid of the Gun connection process.
  Return value A map is returned containing various informations about the connection.
Changelog 1.0: Function introduced.   Examples Obtain information about the connection Info = gun:info(ConnPid).  See also gun(3), gun:open(3), gun:open_unix(3)</description>
    </item>
    
    <item>
      <title>gun:info(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.info/</guid>
      <description>Name gun:info - Obtain information about the connection
Description info(ConnPid) -&amp;gt; Info ConnPid :: pid() Info :: #{ sock_ip =&amp;gt; inet:ip_address(), sock_port =&amp;gt; inet:port_number() }  Obtain information about the connection.
Arguments ConnPid The pid of the Gun connection process.
  Return value A map is returned containing various informations about the connection.
Changelog 1.0: Function introduced.   Examples Obtain information about the connection Info = gun:info(ConnPid).  See also gun(3), gun:open(3), gun:open_unix(3)</description>
    </item>
    
    <item>
      <title>gun:info(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.info/</guid>
      <description>Name gun:info - Obtain information about the connection
Description info(ConnPid) -&amp;gt; Info ConnPid :: pid() Info :: #{ socket =&amp;gt; inet:socket() | ssl:sslsocket(), transport =&amp;gt; tcp | tls, protocol =&amp;gt; http | http2 | ws, sock_ip =&amp;gt; inet:ip_address(), sock_port =&amp;gt; inet:port_number(), origin_host =&amp;gt; inet:hostname() | inet:ip_address(), origin_port =&amp;gt; inet:port_number(), intermediaries =&amp;gt; [Intermediary] } Intermediary :: #{ type =&amp;gt; connect, host =&amp;gt; inet:hostname() | inet:ip_address(), port =&amp;gt; inet:port_number(), transport =&amp;gt; tcp | tls, protocol =&amp;gt; http | http2 }  Obtain information about the connection.</description>
    </item>
    
    <item>
      <title>gun:info(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.info/</guid>
      <description>Name gun:info - Obtain information about the connection
Description info(ConnPid) -&amp;gt; Info ConnPid :: pid() Info :: #{ owner =&amp;gt; pid(), socket =&amp;gt; inet:socket() | ssl:sslsocket(), transport =&amp;gt; tcp | tls, protocol =&amp;gt; http | http2 | socks | ws, sock_ip =&amp;gt; inet:ip_address(), sock_port =&amp;gt; inet:port_number(), origin_host =&amp;gt; inet:hostname() | inet:ip_address(), origin_port =&amp;gt; inet:port_number(), intermediaries =&amp;gt; [Intermediary] } Intermediary :: #{ type =&amp;gt; connect | socks5, host =&amp;gt; inet:hostname() | inet:ip_address(), port =&amp;gt; inet:port_number(), transport =&amp;gt; tcp | tls, protocol =&amp;gt; http | http2 | socks }  Obtain information about the connection.</description>
    </item>
    
    <item>
      <title>gun:open(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.open/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.open/</guid>
      <description>Name gun:open - Open a connection to the given host and port
Description open(Host, Port) -&amp;gt; open(Host, Port, #{}) open(Host, Port, Opts) -&amp;gt; {ok, pid()} | {error, any()} Host :: inet:hostname() | inet:ip_address() Port :: inet:port_number() Opts :: gun:opts()  Open a connection to the given host and port.
Arguments Host Host or IP address to connect to.
 Port Port to connect to.
 Opts Options for this connection.</description>
    </item>
    
    <item>
      <title>gun:open(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.open/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.open/</guid>
      <description>Name gun:open - Open a connection to the given host and port
Description open(Host, Port) -&amp;gt; open(Host, Port, #{}) open(Host, Port, Opts) -&amp;gt; {ok, pid()} | {error, any()} Host :: inet:hostname() | inet:ip_address() Port :: inet:port_number() Opts :: gun:opts()  Open a connection to the given host and port.
Arguments Host Host or IP address to connect to.
 Port Port to connect to.
 Opts Options for this connection.</description>
    </item>
    
    <item>
      <title>gun:open(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.open/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.open/</guid>
      <description>Name gun:open - Open a connection to the given host and port
Description open(Host, Port) -&amp;gt; open(Host, Port, #{}) open(Host, Port, Opts) -&amp;gt; {ok, pid()} | {error, any()} Host :: inet:hostname() | inet:ip_address() Port :: inet:port_number() Opts :: gun:opts()  Open a connection to the given host and port.
Arguments Host Host or IP address to connect to.
 Port Port to connect to.
 Opts Options for this connection.</description>
    </item>
    
    <item>
      <title>gun:open(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.open/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.open/</guid>
      <description>Name gun:open - Open a connection to the given host and port
Description open(Host, Port) -&amp;gt; open(Host, Port, #{}) open(Host, Port, Opts) -&amp;gt; {ok, pid()} | {error, any()} Host :: inet:hostname() | inet:ip_address() Port :: inet:port_number() Opts :: gun:opts()  Open a connection to the given host and port.
Arguments Host Host or IP address to connect to.
 Port Port to connect to.
 Opts Options for this connection.</description>
    </item>
    
    <item>
      <title>gun:open(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.open/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.open/</guid>
      <description>Name gun:open - Open a connection to the given host and port
Description open(Host, Port) -&amp;gt; open(Host, Port, #{}) open(Host, Port, Opts) -&amp;gt; {ok, pid()} | {error, Reason} Host :: inet:hostname() | inet:ip_address() Port :: inet:port_number() Opts :: gun:opts() Reason :: {options, OptName} | {options, {http | http2 | socks | ws, OptName}} | any() OptName :: atom()  Open a connection to the given host and port.
Arguments Host Host or IP address to connect to.</description>
    </item>
    
    <item>
      <title>gun:open_unix(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.open_unix/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.open_unix/</guid>
      <description>Name gun:open_unix - Open a connection to the given Unix domain socket
Description open_unix(SocketPath, Opts) -&amp;gt; {ok, pid()} | {error, any()} SocketPath :: string() Opts :: gun:opts()  Open a connection to the given Unix domain socket.
Arguments SocketPath Path to the Unix domain socket to connect to.
 Opts Options for this connection.
  Return value The pid of the newly created Gun process is returned. Note that this does not indicate that the connection has been successfully opened; the gun_up(3) message will be sent for that.</description>
    </item>
    
    <item>
      <title>gun:open_unix(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.open_unix/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.open_unix/</guid>
      <description>Name gun:open_unix - Open a connection to the given Unix domain socket
Description open_unix(SocketPath, Opts) -&amp;gt; {ok, pid()} | {error, any()} SocketPath :: string() Opts :: gun:opts()  Open a connection to the given Unix domain socket.
Arguments SocketPath Path to the Unix domain socket to connect to.
 Opts Options for this connection.
  Return value The pid of the newly created Gun process is returned. Note that this does not indicate that the connection has been successfully opened; the gun_up(3) message will be sent for that.</description>
    </item>
    
    <item>
      <title>gun:open_unix(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.open_unix/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.open_unix/</guid>
      <description>Name gun:open_unix - Open a connection to the given Unix domain socket
Description open_unix(SocketPath, Opts) -&amp;gt; {ok, pid()} | {error, any()} SocketPath :: string() Opts :: gun:opts()  Open a connection to the given Unix domain socket.
Arguments SocketPath Path to the Unix domain socket to connect to.
 Opts Options for this connection.
  Return value The pid of the newly created Gun process is returned. Note that this does not indicate that the connection has been successfully opened; the gun_up(3) message will be sent for that.</description>
    </item>
    
    <item>
      <title>gun:open_unix(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.open_unix/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.open_unix/</guid>
      <description>Name gun:open_unix - Open a connection to the given Unix domain socket
Description open_unix(SocketPath, Opts) -&amp;gt; {ok, pid()} | {error, any()} SocketPath :: string() Opts :: gun:opts()  Open a connection to the given Unix domain socket.
Arguments SocketPath Path to the Unix domain socket to connect to.
 Opts Options for this connection.
  Return value The pid of the newly created Gun process is returned. Note that this does not indicate that the connection has been successfully opened; the gun_up(3) message will be sent for that.</description>
    </item>
    
    <item>
      <title>gun:open_unix(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.open_unix/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.open_unix/</guid>
      <description>Name gun:open_unix - Open a connection to the given Unix domain socket
Description open_unix(SocketPath, Opts) -&amp;gt; {ok, pid()} | {error, Reason} SocketPath :: string() Opts :: gun:opts() Reason :: {options, OptName} | {options, {http | http2 | socks | ws, OptName}} | any() OptName :: atom()  Open a connection to the given Unix domain socket.
Arguments SocketPath Path to the Unix domain socket to connect to.
 Opts Options for this connection.</description>
    </item>
    
    <item>
      <title>gun:options(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.options/</guid>
      <description>Name gun:options - Query the capabilities of the server or a resource
Description options(ConnPid, Path) -&amp;gt; options(ConnPid, Path, [], #{}). options(ConnPid, Path, Headers) -&amp;gt; options(ConnPid, Path, Headers, #{}) options(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Query the capabilities of the server or a resource.
The special path &amp;quot;*&amp;quot; can be used to obtain information about the server as a whole.</description>
    </item>
    
    <item>
      <title>gun:options(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.options/</guid>
      <description>Name gun:options - Query the capabilities of the server or a resource
Description options(ConnPid, Path) -&amp;gt; options(ConnPid, Path, [], #{}). options(ConnPid, Path, Headers) -&amp;gt; options(ConnPid, Path, Headers, #{}) options(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Query the capabilities of the server or a resource.
The special path &amp;quot;*&amp;quot; can be used to obtain information about the server as a whole.</description>
    </item>
    
    <item>
      <title>gun:options(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.options/</guid>
      <description>Name gun:options - Query the capabilities of the server or a resource
Description options(ConnPid, Path) -&amp;gt; options(ConnPid, Path, [], #{}). options(ConnPid, Path, Headers) -&amp;gt; options(ConnPid, Path, Headers, #{}) options(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Query the capabilities of the server or a resource.
The special path &amp;quot;*&amp;quot; can be used to obtain information about the server as a whole.</description>
    </item>
    
    <item>
      <title>gun:options(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.options/</guid>
      <description>Name gun:options - Query the capabilities of the server or a resource
Description options(ConnPid, Path) -&amp;gt; options(ConnPid, Path, [], #{}). options(ConnPid, Path, Headers) -&amp;gt; options(ConnPid, Path, Headers, #{}) options(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] ReqOpts :: gun:req_opts() StreamRef :: reference()  Query the capabilities of the server or a resource.
The special path &amp;quot;*&amp;quot; can be used to obtain information about the server as a whole.</description>
    </item>
    
    <item>
      <title>gun:options(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.options/</guid>
      <description>Name gun:options - Query the capabilities of the server or a resource
Description options(ConnPid, Path) -&amp;gt; options(ConnPid, Path, [], #{}). options(ConnPid, Path, Headers) -&amp;gt; options(ConnPid, Path, Headers, #{}) options(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() ReqOpts :: gun:req_opts() StreamRef :: reference()  Query the capabilities of the server or a resource.
The special path &amp;quot;*&amp;quot; can be used to obtain information about the server as a whole.</description>
    </item>
    
    <item>
      <title>gun:patch(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.patch/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.patch/</guid>
      <description>Name gun:patch - Apply a set of changes to a resource
Description patch(ConnPid, Path, Headers) -&amp;gt; StreamRef patch(ConnPid, Path, Headers, Body) -&amp;gt; patch(ConnPid, Path, Headers, Body, #{}) patch(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Apply a set of changes to a resource.
The behavior of this function varies depending on whether a body is provided.</description>
    </item>
    
    <item>
      <title>gun:patch(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.patch/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.patch/</guid>
      <description>Name gun:patch - Apply a set of changes to a resource
Description patch(ConnPid, Path, Headers) -&amp;gt; StreamRef patch(ConnPid, Path, Headers, Body) -&amp;gt; patch(ConnPid, Path, Headers, Body, #{}) patch(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Apply a set of changes to a resource.
The behavior of this function varies depending on whether a body is provided.</description>
    </item>
    
    <item>
      <title>gun:patch(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.patch/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.patch/</guid>
      <description>Name gun:patch - Apply a set of changes to a resource
Description patch(ConnPid, Path, Headers) -&amp;gt; StreamRef patch(ConnPid, Path, Headers, Body) -&amp;gt; patch(ConnPid, Path, Headers, Body, #{}) patch(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Apply a set of changes to a resource.
The behavior of this function varies depending on whether a body is provided.</description>
    </item>
    
    <item>
      <title>gun:patch(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.patch/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.patch/</guid>
      <description>Name gun:patch - Apply a set of changes to a resource
Description patch(ConnPid, Path, Headers) -&amp;gt; StreamRef patch(ConnPid, Path, Headers, Body) -&amp;gt; patch(ConnPid, Path, Headers, Body, #{}) patch(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Apply a set of changes to a resource.
The behavior of this function varies depending on whether a body is provided.</description>
    </item>
    
    <item>
      <title>gun:patch(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.patch/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.patch/</guid>
      <description>Name gun:patch - Apply a set of changes to a resource
Description patch(ConnPid, Path, Headers) -&amp;gt; patch(ConnPid, Path, Headers, #{}) patch(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef patch(ConnPid, Path, Headers, Body) -&amp;gt; patch(ConnPid, Path, Headers, Body, #{}) patch(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Apply a set of changes to a resource.</description>
    </item>
    
    <item>
      <title>gun:post(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.post/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.post/</guid>
      <description>Name gun:post - Process the enclosed representation according to a resource&amp;apos;s own semantics
Description post(ConnPid, Path, Headers) -&amp;gt; StreamRef post(ConnPid, Path, Headers, Body) -&amp;gt; post(ConnPid, Path, Headers, Body, #{}) post(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Process the enclosed representation according to a resource&amp;apos;s own semantics.
The behavior of this function varies depending on whether a body is provided.</description>
    </item>
    
    <item>
      <title>gun:post(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.post/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.post/</guid>
      <description>Name gun:post - Process the enclosed representation according to a resource&amp;apos;s own semantics
Description post(ConnPid, Path, Headers) -&amp;gt; StreamRef post(ConnPid, Path, Headers, Body) -&amp;gt; post(ConnPid, Path, Headers, Body, #{}) post(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Process the enclosed representation according to a resource&amp;apos;s own semantics.
The behavior of this function varies depending on whether a body is provided.</description>
    </item>
    
    <item>
      <title>gun:post(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.post/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.post/</guid>
      <description>Name gun:post - Process the enclosed representation according to a resource&amp;apos;s own semantics
Description post(ConnPid, Path, Headers) -&amp;gt; StreamRef post(ConnPid, Path, Headers, Body) -&amp;gt; post(ConnPid, Path, Headers, Body, #{}) post(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Process the enclosed representation according to a resource&amp;apos;s own semantics.
The behavior of this function varies depending on whether a body is provided.</description>
    </item>
    
    <item>
      <title>gun:post(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.post/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.post/</guid>
      <description>Name gun:post - Process the enclosed representation according to a resource&amp;apos;s own semantics
Description post(ConnPid, Path, Headers) -&amp;gt; StreamRef post(ConnPid, Path, Headers, Body) -&amp;gt; post(ConnPid, Path, Headers, Body, #{}) post(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Process the enclosed representation according to a resource&amp;apos;s own semantics.
The behavior of this function varies depending on whether a body is provided.</description>
    </item>
    
    <item>
      <title>gun:post(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.post/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.post/</guid>
      <description>Name gun:post - Process the enclosed representation according to a resource&amp;apos;s own semantics
Description post(ConnPid, Path, Headers) -&amp;gt; post(ConnPid, Path, Headers, #{}) post(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef post(ConnPid, Path, Headers, Body) -&amp;gt; post(ConnPid, Path, Headers, Body, #{}) post(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Process the enclosed representation according to a resource&amp;apos;s own semantics.</description>
    </item>
    
    <item>
      <title>gun:put(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.put/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.put/</guid>
      <description>Name gun:put - Create or replace a resource
Description put(ConnPid, Path, Headers) -&amp;gt; StreamRef put(ConnPid, Path, Headers, Body) -&amp;gt; put(ConnPid, Path, Headers, Body, #{}) put(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Create or replace a resource.
The behavior of this function varies depending on whether a body is provided.
The function put/3 expects either a content-length or content-type header to indicate that a body will be sent afterwards.</description>
    </item>
    
    <item>
      <title>gun:put(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.put/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.put/</guid>
      <description>Name gun:put - Create or replace a resource
Description put(ConnPid, Path, Headers) -&amp;gt; StreamRef put(ConnPid, Path, Headers, Body) -&amp;gt; put(ConnPid, Path, Headers, Body, #{}) put(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Create or replace a resource.
The behavior of this function varies depending on whether a body is provided.
The function put/3 expects either a content-length or content-type header to indicate that a body will be sent afterwards.</description>
    </item>
    
    <item>
      <title>gun:put(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.put/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.put/</guid>
      <description>Name gun:put - Create or replace a resource
Description put(ConnPid, Path, Headers) -&amp;gt; StreamRef put(ConnPid, Path, Headers, Body) -&amp;gt; put(ConnPid, Path, Headers, Body, #{}) put(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Create or replace a resource.
The behavior of this function varies depending on whether a body is provided.
The function put/3 expects either a content-length or content-type header to indicate that a body will be sent afterwards.</description>
    </item>
    
    <item>
      <title>gun:put(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.put/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.put/</guid>
      <description>Name gun:put - Create or replace a resource
Description put(ConnPid, Path, Headers) -&amp;gt; StreamRef put(ConnPid, Path, Headers, Body) -&amp;gt; put(ConnPid, Path, Headers, Body, #{}) put(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Create or replace a resource.
The behavior of this function varies depending on whether a body is provided.
The function put/3 expects either a content-length or content-type header to indicate that a body will be sent afterwards.</description>
    </item>
    
    <item>
      <title>gun:put(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.put/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.put/</guid>
      <description>Name gun:put - Create or replace a resource
Description put(ConnPid, Path, Headers) -&amp;gt; put(ConnPid, Path, Headers, #{}) put(ConnPid, Path, Headers, ReqOpts) -&amp;gt; StreamRef put(ConnPid, Path, Headers, Body) -&amp;gt; put(ConnPid, Path, Headers, Body, #{}) put(ConnPid, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Create or replace a resource.
The behavior of this function varies depending on whether a body is provided.</description>
    </item>
    
    <item>
      <title>gun:request(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.request/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.request/</guid>
      <description>Name gun:request - Perform the given request
Description request(ConnPid, Method, Path, Headers) -&amp;gt; StreamRef request(ConnPid, Method, Path, Headers, Body) -&amp;gt; request(ConnPid, Method, Path, Headers, Body, #{}) request(ConnPid, Method, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Method :: binary() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Perform the given request.
This is a general purpose function that should only be used when other method-specific functions do not apply.</description>
    </item>
    
    <item>
      <title>gun:request(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.request/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.request/</guid>
      <description>Name gun:request - Perform the given request
Description request(ConnPid, Method, Path, Headers) -&amp;gt; StreamRef request(ConnPid, Method, Path, Headers, Body) -&amp;gt; request(ConnPid, Method, Path, Headers, Body, #{}) request(ConnPid, Method, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Method :: binary() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Perform the given request.
This is a general purpose function that should only be used when other method-specific functions do not apply.</description>
    </item>
    
    <item>
      <title>gun:request(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.request/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.request/</guid>
      <description>Name gun:request - Perform the given request
Description request(ConnPid, Method, Path, Headers) -&amp;gt; StreamRef request(ConnPid, Method, Path, Headers, Body) -&amp;gt; request(ConnPid, Method, Path, Headers, Body, #{}) request(ConnPid, Method, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Method :: binary() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Perform the given request.
This is a general purpose function that should only be used when other method-specific functions do not apply.</description>
    </item>
    
    <item>
      <title>gun:request(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.request/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.request/</guid>
      <description>Name gun:request - Perform the given request
Description request(ConnPid, Method, Path, Headers) -&amp;gt; StreamRef request(ConnPid, Method, Path, Headers, Body) -&amp;gt; request(ConnPid, Method, Path, Headers, Body, #{}) request(ConnPid, Method, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Method :: binary() Path :: iodata() Headers :: [{binary(), iodata()}] Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Perform the given request.
This is a general purpose function that should only be used when other method-specific functions do not apply.</description>
    </item>
    
    <item>
      <title>gun:request(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.request/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.request/</guid>
      <description>Name gun:request - Perform the given request
Description request(ConnPid, Method, Path, Headers, Body) -&amp;gt; request(ConnPid, Method, Path, Headers, Body, #{}) request(ConnPid, Method, Path, Headers, Body, ReqOpts) -&amp;gt; StreamRef ConnPid :: pid() Method :: binary() Path :: iodata() Headers :: gun:req_headers() Body :: iodata() ReqOpts :: gun:req_opts() StreamRef :: reference()  Perform the given request.
This is a general purpose function that should only be used when other method-specific functions do not apply.</description>
    </item>
    
    <item>
      <title>gun:set_owner(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.set_owner/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.set_owner/</guid>
      <description>Name gun:set_owner - Set a new owner for the connection
Description set_owner(ConnPid, OwnerPid) -&amp;gt; ok ConnPid :: pid() OwnerPid :: pid()  Set a new owner for the connection.
Only the current owner of the connection can set a new owner.
Gun monitors the owner of the connection and automatically shuts down gracefully when the owner exits.
Arguments ConnPid The pid of the Gun connection process.
 OwnerPid The pid of the new owner for the connection.</description>
    </item>
    
    <item>
      <title>gun:shutdown(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.shutdown/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.shutdown/</guid>
      <description>Name gun:shutdown - Gracefully close the connection
Description shutdown(ConnPid) -&amp;gt; ok ConnPid :: pid()  Gracefully close the connection.
Gun will wait for up to closing_timeout milliseconds before brutally closing the connection. The graceful shutdown mechanism varies between the different protocols:
For HTTP/1.1 there is no such mechanism and Gun will close the connection once the current response is received. Any pipelined requests are immediately terminated.  For HTTP/2 Gun will send a GOAWAY frame and wait for the existing streams to terminate.</description>
    </item>
    
    <item>
      <title>gun:stream_info(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.stream_info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.stream_info/</guid>
      <description>Name gun:stream_info - Obtain information about a stream
Description stream_info(ConnPid, StreamRef) -&amp;gt; {ok, undefined | Info} | {error, not_connected} ConnPid :: pid() StreamRef :: reference() Info :: #{ ref =&amp;gt; reference(), reply_to =&amp;gt; pid(), state =&amp;gt; running | stopping }  Obtain information about a stream.
Arguments ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
  Return value A map is returned containing various informations about the stream.</description>
    </item>
    
    <item>
      <title>gun:update_flow(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.update_flow/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.update_flow/</guid>
      <description>Name gun:update_flow - Update a stream&amp;apos;s flow control value
Description update_flow(ConnPid, StreamRef, Flow) -&amp;gt; ok ConnPid :: pid() StreamRef :: reference() Flow :: pos_integer()  Update a stream&amp;apos;s flow control value.
The flow value can only ever be incremented.
This function does nothing for streams that have flow control disabled (which is the default).
Arguments ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.</description>
    </item>
    
    <item>
      <title>gun:ws_send(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.ws_send/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.ws_send/</guid>
      <description>Name gun:ws_send - Send Websocket frames
Description ws_send(ConnPid, Frames) -&amp;gt; ok ConnPid :: pid() Frames :: Frame | [Frame] Frame :: close | ping | pong | {text | binary | close | ping | pong, iodata()} | {close, non_neg_integer(), iodata()}  Send Websocket frames.
The connection must first be upgraded to Websocket using the function gun:ws_upgrade(3).
Arguments ConnPid The pid of the Gun connection process.
 Frames A Websocket frame.</description>
    </item>
    
    <item>
      <title>gun:ws_send(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.ws_send/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.ws_send/</guid>
      <description>Name gun:ws_send - Send Websocket frames
Description ws_send(ConnPid, Frames) -&amp;gt; ok ConnPid :: pid() Frames :: Frame | [Frame] Frame :: close | ping | pong | {text | binary | close | ping | pong, iodata()} | {close, non_neg_integer(), iodata()}  Send Websocket frames.
The connection must first be upgraded to Websocket using the function gun:ws_upgrade(3).
Arguments ConnPid The pid of the Gun connection process.
 Frames A Websocket frame.</description>
    </item>
    
    <item>
      <title>gun:ws_send(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.ws_send/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.ws_send/</guid>
      <description>Name gun:ws_send - Send Websocket frames
Description ws_send(ConnPid, Frames) -&amp;gt; ok ConnPid :: pid() Frames :: Frame | [Frame] Frame :: close | ping | pong | {text | binary | close | ping | pong, iodata()} | {close, non_neg_integer(), iodata()}  Send Websocket frames.
The connection must first be upgraded to Websocket using the function gun:ws_upgrade(3).
Arguments ConnPid The pid of the Gun connection process.
 Frames A Websocket frame.</description>
    </item>
    
    <item>
      <title>gun:ws_send(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.ws_send/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.ws_send/</guid>
      <description>Name gun:ws_send - Send Websocket frames
Description ws_send(ConnPid, Frames) -&amp;gt; ok ConnPid :: pid() Frames :: Frame | [Frame] Frame :: close | ping | pong | {text | binary | close | ping | pong, iodata()} | {close, non_neg_integer(), iodata()}  Send Websocket frames.
The connection must first be upgraded to Websocket using the function gun:ws_upgrade(3).
Arguments ConnPid The pid of the Gun connection process.
 Frames A Websocket frame.</description>
    </item>
    
    <item>
      <title>gun:ws_send(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.ws_send/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.ws_send/</guid>
      <description>Name gun:ws_send - Send Websocket frames
Description ws_send(ConnPid, Frames) -&amp;gt; ok ConnPid :: pid() Frames :: Frame | [Frame] Frame :: close | ping | pong | {text | binary | close | ping | pong, iodata()} | {close, non_neg_integer(), iodata()}  Send Websocket frames.
The connection must first be upgraded to Websocket using the function gun:ws_upgrade(3).
Arguments ConnPid The pid of the Gun connection process.
 Frames One or more Websocket frame(s).</description>
    </item>
    
    <item>
      <title>gun:ws_upgrade(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun.ws_upgrade/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun.ws_upgrade/</guid>
      <description>Name gun:ws_upgrade - Upgrade to Websocket
Description ws_upgrade(ConnPid, Path) -&amp;gt; ws_upgrade(ConnPid, Path, []) ws_upgrade(ConnPid, Path, Headers) -&amp;gt; StreamRef ws_upgrade(ConnPid, Path, Headers, WsOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] WsOpts :: gun:ws_opts StreamRef :: reference()  Upgrade to Websocket.
The behavior of this function depends on the protocol selected.
HTTP/1.1 cannot handle Websocket and HTTP requests concurrently. The upgrade, if successful, will result in the complete takeover of the connection.</description>
    </item>
    
    <item>
      <title>gun:ws_upgrade(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun.ws_upgrade/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun.ws_upgrade/</guid>
      <description>Name gun:ws_upgrade - Upgrade to Websocket
Description ws_upgrade(ConnPid, Path) -&amp;gt; ws_upgrade(ConnPid, Path, []) ws_upgrade(ConnPid, Path, Headers) -&amp;gt; StreamRef ws_upgrade(ConnPid, Path, Headers, WsOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] WsOpts :: gun:ws_opts StreamRef :: reference()  Upgrade to Websocket.
The behavior of this function depends on the protocol selected.
HTTP/1.1 cannot handle Websocket and HTTP requests concurrently. The upgrade, if successful, will result in the complete takeover of the connection.</description>
    </item>
    
    <item>
      <title>gun:ws_upgrade(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun.ws_upgrade/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun.ws_upgrade/</guid>
      <description>Name gun:ws_upgrade - Upgrade to Websocket
Description ws_upgrade(ConnPid, Path) -&amp;gt; ws_upgrade(ConnPid, Path, []) ws_upgrade(ConnPid, Path, Headers) -&amp;gt; StreamRef ws_upgrade(ConnPid, Path, Headers, WsOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] WsOpts :: gun:ws_opts StreamRef :: reference()  Upgrade to Websocket.
The behavior of this function depends on the protocol selected.
HTTP/1.1 cannot handle Websocket and HTTP requests concurrently. The upgrade, if successful, will result in the complete takeover of the connection.</description>
    </item>
    
    <item>
      <title>gun:ws_upgrade(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun.ws_upgrade/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun.ws_upgrade/</guid>
      <description>Name gun:ws_upgrade - Upgrade to Websocket
Description ws_upgrade(ConnPid, Path) -&amp;gt; ws_upgrade(ConnPid, Path, []) ws_upgrade(ConnPid, Path, Headers) -&amp;gt; StreamRef ws_upgrade(ConnPid, Path, Headers, WsOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: [{binary(), iodata()}] WsOpts :: gun:ws_opts StreamRef :: reference()  Upgrade to Websocket.
The behavior of this function depends on the protocol selected.
HTTP/1.1 cannot handle Websocket and HTTP requests concurrently. The upgrade, if successful, will result in the complete takeover of the connection.</description>
    </item>
    
    <item>
      <title>gun:ws_upgrade(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun.ws_upgrade/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun.ws_upgrade/</guid>
      <description>Name gun:ws_upgrade - Upgrade to Websocket
Description ws_upgrade(ConnPid, Path) -&amp;gt; ws_upgrade(ConnPid, Path, []) ws_upgrade(ConnPid, Path, Headers) -&amp;gt; StreamRef ws_upgrade(ConnPid, Path, Headers, WsOpts) -&amp;gt; StreamRef ConnPid :: pid() Path :: iodata() Headers :: gun:req_headers() WsOpts :: gun:ws_opts StreamRef :: reference()  Upgrade to Websocket.
The behavior of this function depends on the protocol selected.
HTTP/1.1 cannot handle Websocket and HTTP requests concurrently. The upgrade, if successful, will result in the complete takeover of the connection.</description>
    </item>
    
    <item>
      <title>gun_data(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_data/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun_data/</guid>
      <description>Name gun_data - Response body
Description {gun_data, ConnPid, StreamRef, IsFin, Data} ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Data :: binary()  Response body.
This message informs the relevant process that the server sent a all or part of the body for the response to the original request.
A data message is always preceded by a response message.
The response body may be terminated either by a data message with the flag fin set or by a gun_trailers(3) message.</description>
    </item>
    
    <item>
      <title>gun_data(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun_data/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun_data/</guid>
      <description>Name gun_data - Response body
Description {gun_data, ConnPid, StreamRef, IsFin, Data} ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Data :: binary()  Response body.
This message informs the relevant process that the server sent a all or part of the body for the response to the original request.
A data message is always preceded by a response message.
The response body may be terminated either by a data message with the flag fin set or by a gun_trailers(3) message.</description>
    </item>
    
    <item>
      <title>gun_data(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun_data/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun_data/</guid>
      <description>Name gun_data - Response body
Description {gun_data, ConnPid, StreamRef, IsFin, Data} ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Data :: binary()  Response body.
This message informs the relevant process that the server sent a all or part of the body for the response to the original request.
A data message is always preceded by a response message.
The response body may be terminated either by a data message with the flag fin set or by a gun_trailers(3) message.</description>
    </item>
    
    <item>
      <title>gun_data(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun_data/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun_data/</guid>
      <description>Name gun_data - Response body
Description {gun_data, ConnPid, StreamRef, IsFin, Data} ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Data :: binary()  Response body.
This message informs the relevant process that the server sent a all or part of the body for the response to the original request.
A data message is always preceded by a response message.
The response body may be terminated either by a data message with the flag fin set or by a gun_trailers(3) message.</description>
    </item>
    
    <item>
      <title>gun_data(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_data/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun_data/</guid>
      <description>Name gun_data - Response body
Description {gun_data, ConnPid, StreamRef, IsFin, Data} ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Data :: binary()  Response body.
This message informs the relevant process that the server sent a all or part of the body for the response to the original request.
A data message is always preceded by a response message.
The response body may be terminated either by a data message with the flag fin set or by a gun_trailers(3) message.</description>
    </item>
    
    <item>
      <title>gun_down(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_down/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun_down/</guid>
      <description>Name gun_down - The connection is down
Description {gun_down, ConnPid, Protocol, Reason, KilledStreams, UnprocessedStreams} ConnPid :: pid() Protocol :: http | http2 | ws Reason :: any() KilledStreams :: [reference()] UnprocessedStreams :: [reference()]  The connection is down.
This message informs the owner process that the connection was lost. Depending on the retry and retry_timeout options Gun may automatically attempt to reconnect.
When the connection goes back up, Gun will not attempt to retry requests.</description>
    </item>
    
    <item>
      <title>gun_down(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun_down/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun_down/</guid>
      <description>Name gun_down - The connection is down
Description {gun_down, ConnPid, Protocol, Reason, KilledStreams, UnprocessedStreams} ConnPid :: pid() Protocol :: http | http2 | ws Reason :: any() KilledStreams :: [reference()] UnprocessedStreams :: [reference()]  The connection is down.
This message informs the owner process that the connection was lost. Depending on the retry and retry_timeout options Gun may automatically attempt to reconnect.
When the connection goes back up, Gun will not attempt to retry requests.</description>
    </item>
    
    <item>
      <title>gun_down(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun_down/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun_down/</guid>
      <description>Name gun_down - The connection is down
Description {gun_down, ConnPid, Protocol, Reason, KilledStreams, UnprocessedStreams} ConnPid :: pid() Protocol :: http | http2 | ws Reason :: any() KilledStreams :: [reference()] UnprocessedStreams :: [reference()]  The connection is down.
This message informs the owner process that the connection was lost. Depending on the retry and retry_timeout options Gun may automatically attempt to reconnect.
When the connection goes back up, Gun will not attempt to retry requests.</description>
    </item>
    
    <item>
      <title>gun_down(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun_down/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun_down/</guid>
      <description>Name gun_down - The connection is down
Description {gun_down, ConnPid, Protocol, Reason, KilledStreams, UnprocessedStreams} ConnPid :: pid() Protocol :: http | http2 | ws Reason :: any() KilledStreams :: [reference()] UnprocessedStreams :: [reference()]  The connection is down.
This message informs the owner process that the connection was lost. Depending on the retry and retry_timeout options Gun may automatically attempt to reconnect.
When the connection goes back up, Gun will not attempt to retry requests.</description>
    </item>
    
    <item>
      <title>gun_down(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_down/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun_down/</guid>
      <description>Name gun_down - The connection is down
Description {gun_down, ConnPid, Protocol, Reason, KilledStreams} ConnPid :: pid() Protocol :: http | http2 | socks | ws Reason :: any() KilledStreams :: [reference()]  The connection is down.
This message informs the owner process that the connection was lost. Depending on the retry and retry_timeout options Gun may automatically attempt to reconnect.
When the connection goes back up, Gun will not attempt to retry requests.</description>
    </item>
    
    <item>
      <title>gun_error(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_error/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun_error/</guid>
      <description>Name gun_error - Stream or connection-wide error
Description {gun_error, ConnPid, StreamRef, Reason} {gun_error, ConnPid, Reason} ConnPid :: pid() StreamRef :: reference() Reason :: any()  Stream or connection-wide error.
These messages inform the relevant process that an error occurred. A reference is given when the error pertains to a specific stream. Connection-wide errors do not imply that the connection is no longer usable, they are used for all errors that are not specific to a stream.</description>
    </item>
    
    <item>
      <title>gun_error(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun_error/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun_error/</guid>
      <description>Name gun_error - Stream or connection-wide error
Description {gun_error, ConnPid, StreamRef, Reason} {gun_error, ConnPid, Reason} ConnPid :: pid() StreamRef :: reference() Reason :: any()  Stream or connection-wide error.
These messages inform the relevant process that an error occurred. A reference is given when the error pertains to a specific stream. Connection-wide errors do not imply that the connection is no longer usable, they are used for all errors that are not specific to a stream.</description>
    </item>
    
    <item>
      <title>gun_error(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun_error/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun_error/</guid>
      <description>Name gun_error - Stream or connection-wide error
Description {gun_error, ConnPid, StreamRef, Reason} {gun_error, ConnPid, Reason} ConnPid :: pid() StreamRef :: reference() Reason :: any()  Stream or connection-wide error.
These messages inform the relevant process that an error occurred. A reference is given when the error pertains to a specific stream. Connection-wide errors do not imply that the connection is no longer usable, they are used for all errors that are not specific to a stream.</description>
    </item>
    
    <item>
      <title>gun_error(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun_error/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun_error/</guid>
      <description>Name gun_error - Stream or connection-wide error
Description {gun_error, ConnPid, StreamRef, Reason} {gun_error, ConnPid, Reason} ConnPid :: pid() StreamRef :: reference() Reason :: any()  Stream or connection-wide error.
These messages inform the relevant process that an error occurred. A reference is given when the error pertains to a specific stream. Connection-wide errors do not imply that the connection is no longer usable, they are used for all errors that are not specific to a stream.</description>
    </item>
    
    <item>
      <title>gun_error(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_error/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun_error/</guid>
      <description>Name gun_error - Stream or connection-wide error
Description {gun_error, ConnPid, StreamRef, Reason} {gun_error, ConnPid, Reason} ConnPid :: pid() StreamRef :: reference() Reason :: any()  Stream or connection-wide error.
These messages inform the relevant process that an error occurred. A reference is given when the error pertains to a specific stream. Connection-wide errors do not imply that the connection is no longer usable, they are used for all errors that are not specific to a stream.</description>
    </item>
    
    <item>
      <title>gun_inform(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_inform/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun_inform/</guid>
      <description>Name gun_inform - Informational response
Description {gun_inform, ConnPid, StreamRef, Status, Headers} ConnPid :: pid() StreamRef :: reference() Status :: 100..199 Headers :: [{binary(), binary()}]  Informational response.
This message informs the relevant process that the server sent an informational response to the original request.
Informational responses are only intermediate responses and provide no guarantees as to what the final response will be. An informational response always precedes the response to the original request.</description>
    </item>
    
    <item>
      <title>gun_inform(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun_inform/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun_inform/</guid>
      <description>Name gun_inform - Informational response
Description {gun_inform, ConnPid, StreamRef, Status, Headers} ConnPid :: pid() StreamRef :: reference() Status :: 100..199 Headers :: [{binary(), binary()}]  Informational response.
This message informs the relevant process that the server sent an informational response to the original request.
Informational responses are only intermediate responses and provide no guarantees as to what the final response will be. An informational response always precedes the response to the original request.</description>
    </item>
    
    <item>
      <title>gun_inform(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun_inform/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun_inform/</guid>
      <description>Name gun_inform - Informational response
Description {gun_inform, ConnPid, StreamRef, Status, Headers} ConnPid :: pid() StreamRef :: reference() Status :: 100..199 Headers :: [{binary(), binary()}]  Informational response.
This message informs the relevant process that the server sent an informational response to the original request.
Informational responses are only intermediate responses and provide no guarantees as to what the final response will be. An informational response always precedes the response to the original request.</description>
    </item>
    
    <item>
      <title>gun_inform(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun_inform/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun_inform/</guid>
      <description>Name gun_inform - Informational response
Description {gun_inform, ConnPid, StreamRef, Status, Headers} ConnPid :: pid() StreamRef :: reference() Status :: 100..199 Headers :: [{binary(), binary()}]  Informational response.
This message informs the relevant process that the server sent an informational response to the original request.
Informational responses are only intermediate responses and provide no guarantees as to what the final response will be. An informational response always precedes the response to the original request.</description>
    </item>
    
    <item>
      <title>gun_inform(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_inform/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun_inform/</guid>
      <description>Name gun_inform - Informational response
Description {gun_inform, ConnPid, StreamRef, Status, Headers} ConnPid :: pid() StreamRef :: reference() Status :: 100..199 Headers :: [{binary(), binary()}]  Informational response.
This message informs the relevant process that the server sent an informational response to the original request.
Informational responses are only intermediate responses and provide no guarantees as to what the final response will be. An informational response always precedes the response to the original request.</description>
    </item>
    
    <item>
      <title>gun_push(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_push/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun_push/</guid>
      <description>Name gun_push - Server-initiated push
Description {gun_push, ConnPid, StreamRef, NewStreamRef, Method, URI, Headers} ConnPid :: pid() StreamRef :: reference() NewStreamRef :: reference() Method :: binary() URI :: binary() Headers :: [{binary(), binary()}]  Server-initiated push.
This message informs the relevant process that the server is pushing a resource related to the effective target URI of the original request.
A server-initiated push message always precedes the response to the original request.</description>
    </item>
    
    <item>
      <title>gun_push(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun_push/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun_push/</guid>
      <description>Name gun_push - Server-initiated push
Description {gun_push, ConnPid, StreamRef, NewStreamRef, Method, URI, Headers} ConnPid :: pid() StreamRef :: reference() NewStreamRef :: reference() Method :: binary() URI :: binary() Headers :: [{binary(), binary()}]  Server-initiated push.
This message informs the relevant process that the server is pushing a resource related to the effective target URI of the original request.
A server-initiated push message always precedes the response to the original request.</description>
    </item>
    
    <item>
      <title>gun_push(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun_push/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun_push/</guid>
      <description>Name gun_push - Server-initiated push
Description {gun_push, ConnPid, StreamRef, NewStreamRef, Method, URI, Headers} ConnPid :: pid() StreamRef :: reference() NewStreamRef :: reference() Method :: binary() URI :: binary() Headers :: [{binary(), binary()}]  Server-initiated push.
This message informs the relevant process that the server is pushing a resource related to the effective target URI of the original request.
A server-initiated push message always precedes the response to the original request.</description>
    </item>
    
    <item>
      <title>gun_push(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun_push/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun_push/</guid>
      <description>Name gun_push - Server-initiated push
Description {gun_push, ConnPid, StreamRef, NewStreamRef, Method, URI, Headers} ConnPid :: pid() StreamRef :: reference() NewStreamRef :: reference() Method :: binary() URI :: binary() Headers :: [{binary(), binary()}]  Server-initiated push.
This message informs the relevant process that the server is pushing a resource related to the effective target URI of the original request.
A server-initiated push message always precedes the response to the original request.</description>
    </item>
    
    <item>
      <title>gun_push(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_push/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun_push/</guid>
      <description>Name gun_push - Server-initiated push
Description {gun_push, ConnPid, StreamRef, NewStreamRef, Method, URI, Headers} ConnPid :: pid() StreamRef :: reference() NewStreamRef :: reference() Method :: binary() URI :: binary() Headers :: [{binary(), binary()}]  Server-initiated push.
This message informs the relevant process that the server is pushing a resource related to the effective target URI of the original request.
A server-initiated push message always precedes the response to the original request.</description>
    </item>
    
    <item>
      <title>gun_response(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_response/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun_response/</guid>
      <description>Name gun_response - Response
Description {gun_response, ConnPid, StreamRef, IsFin, Status, Headers} ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Status :: non_neg_integer() Headers :: [{binary(), binary()}]  Response.
This message informs the relevant process that the server sent a response to the original request.
Elements ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
 IsFin Whether this message terminates the response.</description>
    </item>
    
    <item>
      <title>gun_response(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun_response/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun_response/</guid>
      <description>Name gun_response - Response
Description {gun_response, ConnPid, StreamRef, IsFin, Status, Headers} ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Status :: non_neg_integer() Headers :: [{binary(), binary()}]  Response.
This message informs the relevant process that the server sent a response to the original request.
Elements ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
 IsFin Whether this message terminates the response.</description>
    </item>
    
    <item>
      <title>gun_response(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun_response/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun_response/</guid>
      <description>Name gun_response - Response
Description {gun_response, ConnPid, StreamRef, IsFin, Status, Headers} ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Status :: non_neg_integer() Headers :: [{binary(), binary()}]  Response.
This message informs the relevant process that the server sent a response to the original request.
Elements ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
 IsFin Whether this message terminates the response.</description>
    </item>
    
    <item>
      <title>gun_response(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun_response/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun_response/</guid>
      <description>Name gun_response - Response
Description {gun_response, ConnPid, StreamRef, IsFin, Status, Headers} ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Status :: non_neg_integer() Headers :: [{binary(), binary()}]  Response.
This message informs the relevant process that the server sent a response to the original request.
Elements ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
 IsFin Whether this message terminates the response.</description>
    </item>
    
    <item>
      <title>gun_response(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_response/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun_response/</guid>
      <description>Name gun_response - Response
Description {gun_response, ConnPid, StreamRef, IsFin, Status, Headers} ConnPid :: pid() StreamRef :: reference() IsFin :: fin | nofin Status :: non_neg_integer() Headers :: [{binary(), binary()}]  Response.
This message informs the relevant process that the server sent a response to the original request.
Elements ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
 IsFin Whether this message terminates the response.</description>
    </item>
    
    <item>
      <title>gun_socks_up(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_socks_up/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun_socks_up/</guid>
      <description>Name gun_socks_up - The Socks connection is up
Description {gun_socks_up, ConnPid, Protocol} ConnPid :: pid() Protocol :: http | http2 | socks  The Socks connection is up.
This message informs the owner/calling process that the connection completed through the configured Socks proxy.
If Gun is configured to connect to another Socks server, then the connection is not usable yet. One or more gun_socks_up(3) messages will follow.
Otherwise, Gun will start processing the messages it received while waiting for the connection to be up.</description>
    </item>
    
    <item>
      <title>gun_trailers(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_trailers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun_trailers/</guid>
      <description>Name gun_trailers - Response trailers
Description {gun_trailers, ConnPid, StreamRef, Headers} ConnPid :: pid() StreamRef :: reference() Headers :: [{binary(), binary()}]  Response trailers.
This message informs the relevant process that the server sent response trailers for the response to the original request.
A trailers message terminates the response.
Elements ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
 Headers Trailing headers sent after the response body.</description>
    </item>
    
    <item>
      <title>gun_trailers(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun_trailers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun_trailers/</guid>
      <description>Name gun_trailers - Response trailers
Description {gun_trailers, ConnPid, StreamRef, Headers} ConnPid :: pid() StreamRef :: reference() Headers :: [{binary(), binary()}]  Response trailers.
This message informs the relevant process that the server sent response trailers for the response to the original request.
A trailers message terminates the response.
Elements ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
 Headers Trailing headers sent after the response body.</description>
    </item>
    
    <item>
      <title>gun_trailers(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun_trailers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun_trailers/</guid>
      <description>Name gun_trailers - Response trailers
Description {gun_trailers, ConnPid, StreamRef, Headers} ConnPid :: pid() StreamRef :: reference() Headers :: [{binary(), binary()}]  Response trailers.
This message informs the relevant process that the server sent response trailers for the response to the original request.
A trailers message terminates the response.
Elements ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
 Headers Trailing headers sent after the response body.</description>
    </item>
    
    <item>
      <title>gun_trailers(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun_trailers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun_trailers/</guid>
      <description>Name gun_trailers - Response trailers
Description {gun_trailers, ConnPid, StreamRef, Headers} ConnPid :: pid() StreamRef :: reference() Headers :: [{binary(), binary()}]  Response trailers.
This message informs the relevant process that the server sent response trailers for the response to the original request.
A trailers message terminates the response.
Elements ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
 Headers Trailing headers sent after the response body.</description>
    </item>
    
    <item>
      <title>gun_trailers(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_trailers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun_trailers/</guid>
      <description>Name gun_trailers - Response trailers
Description {gun_trailers, ConnPid, StreamRef, Headers} ConnPid :: pid() StreamRef :: reference() Headers :: [{binary(), binary()}]  Response trailers.
This message informs the relevant process that the server sent response trailers for the response to the original request.
A trailers message terminates the response.
Elements ConnPid The pid of the Gun connection process.
 StreamRef Identifier of the stream for the original request.
 Headers Trailing headers sent after the response body.</description>
    </item>
    
    <item>
      <title>gun_up(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_up/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun_up/</guid>
      <description>Name gun_up - The connection is up
Description {gun_up, ConnPid, Protocol} ConnPid :: pid() Protocol :: http | http2  The connection is up.
This message informs the owner process that the connection or reconnection completed.
Gun will now start processing the messages it received while waiting for the connection to be up. If this is a reconnection, then this may not be desirable for all requests. Those requests should be cancelled when the connection goes down, and any subsequent messages ignored.</description>
    </item>
    
    <item>
      <title>gun_up(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun_up/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun_up/</guid>
      <description>Name gun_up - The connection is up
Description {gun_up, ConnPid, Protocol} ConnPid :: pid() Protocol :: http | http2  The connection is up.
This message informs the owner process that the connection or reconnection completed.
Gun will now start processing the messages it received while waiting for the connection to be up. If this is a reconnection, then this may not be desirable for all requests. Those requests should be cancelled when the connection goes down, and any subsequent messages ignored.</description>
    </item>
    
    <item>
      <title>gun_up(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun_up/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun_up/</guid>
      <description>Name gun_up - The connection is up
Description {gun_up, ConnPid, Protocol} ConnPid :: pid() Protocol :: http | http2  The connection is up.
This message informs the owner process that the connection or reconnection completed.
Gun will now start processing the messages it received while waiting for the connection to be up. If this is a reconnection, then this may not be desirable for all requests. Those requests should be cancelled when the connection goes down, and any subsequent messages ignored.</description>
    </item>
    
    <item>
      <title>gun_up(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun_up/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun_up/</guid>
      <description>Name gun_up - The connection is up
Description {gun_up, ConnPid, Protocol} ConnPid :: pid() Protocol :: http | http2  The connection is up.
This message informs the owner process that the connection or reconnection completed.
Gun will now start processing the messages it received while waiting for the connection to be up. If this is a reconnection, then this may not be desirable for all requests. Those requests should be cancelled when the connection goes down, and any subsequent messages ignored.</description>
    </item>
    
    <item>
      <title>gun_up(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_up/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun_up/</guid>
      <description>Name gun_up - The connection is up
Description {gun_up, ConnPid, Protocol} ConnPid :: pid() Protocol :: http | http2 | socks  The connection is up.
This message informs the owner process that the connection or reconnection completed.
If Gun is configured to connect to a Socks server, then the connection is not usable yet. One or more gun_socks_up(3) messages will follow.
Otherwise, Gun will start processing the messages it received while waiting for the connection to be up.</description>
    </item>
    
    <item>
      <title>gun_upgrade(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_upgrade/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun_upgrade/</guid>
      <description>Name gun_upgrade - Successful protocol upgrade
Description {gun_upgrade, ConnPid, StreamRef, Protocols, Headers} ConnPid :: pid() StreamRef :: reference() Protocols :: [&amp;lt;&amp;lt;&#34;websocket&#34;&amp;gt;&amp;gt;] Headers :: [{binary(), binary()}]  Successful protocol upgrade.
This message informs the relevant process that the server accepted to upgrade to one or more protocols given in the original request.
The exact semantics of this message depend on the original protocol. HTTP/1.1 upgrades apply to the entire connection. HTTP/2 uses a different mechanism which allows switching specific streams to a different protocol.</description>
    </item>
    
    <item>
      <title>gun_upgrade(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun_upgrade/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun_upgrade/</guid>
      <description>Name gun_upgrade - Successful protocol upgrade
Description {gun_upgrade, ConnPid, StreamRef, Protocols, Headers} ConnPid :: pid() StreamRef :: reference() Protocols :: [&amp;lt;&amp;lt;&#34;websocket&#34;&amp;gt;&amp;gt;] Headers :: [{binary(), binary()}]  Successful protocol upgrade.
This message informs the relevant process that the server accepted to upgrade to one or more protocols given in the original request.
The exact semantics of this message depend on the original protocol. HTTP/1.1 upgrades apply to the entire connection. HTTP/2 uses a different mechanism which allows switching specific streams to a different protocol.</description>
    </item>
    
    <item>
      <title>gun_upgrade(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun_upgrade/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun_upgrade/</guid>
      <description>Name gun_upgrade - Successful protocol upgrade
Description {gun_upgrade, ConnPid, StreamRef, Protocols, Headers} ConnPid :: pid() StreamRef :: reference() Protocols :: [&amp;lt;&amp;lt;&#34;websocket&#34;&amp;gt;&amp;gt;] Headers :: [{binary(), binary()}]  Successful protocol upgrade.
This message informs the relevant process that the server accepted to upgrade to one or more protocols given in the original request.
The exact semantics of this message depend on the original protocol. HTTP/1.1 upgrades apply to the entire connection. HTTP/2 uses a different mechanism which allows switching specific streams to a different protocol.</description>
    </item>
    
    <item>
      <title>gun_upgrade(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun_upgrade/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun_upgrade/</guid>
      <description>Name gun_upgrade - Successful protocol upgrade
Description {gun_upgrade, ConnPid, StreamRef, Protocols, Headers} ConnPid :: pid() StreamRef :: reference() Protocols :: [&amp;lt;&amp;lt;&#34;websocket&#34;&amp;gt;&amp;gt;] Headers :: [{binary(), binary()}]  Successful protocol upgrade.
This message informs the relevant process that the server accepted to upgrade to one or more protocols given in the original request.
The exact semantics of this message depend on the original protocol. HTTP/1.1 upgrades apply to the entire connection. HTTP/2 uses a different mechanism which allows switching specific streams to a different protocol.</description>
    </item>
    
    <item>
      <title>gun_upgrade(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_upgrade/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun_upgrade/</guid>
      <description>Name gun_upgrade - Successful protocol upgrade
Description {gun_upgrade, ConnPid, StreamRef, Protocols, Headers} ConnPid :: pid() StreamRef :: reference() Protocols :: [&amp;lt;&amp;lt;&#34;websocket&#34;&amp;gt;&amp;gt;] Headers :: [{binary(), binary()}]  Successful protocol upgrade.
This message informs the relevant process that the server accepted to upgrade to one or more protocols given in the original request.
The exact semantics of this message depend on the original protocol. HTTP/1.1 upgrades apply to the entire connection. HTTP/2 uses a different mechanism which allows switching specific streams to a different protocol.</description>
    </item>
    
    <item>
      <title>gun_ws(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.0/manual/gun_ws/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.0/manual/gun_ws/</guid>
      <description>Name gun_ws - Websocket frame
Description {gun_ws, ConnPid, StreamRef, Frame} ConnPid :: pid() StreamRef :: reference() Frame :: close | {text | binary | close, binary()} | {close, non_neg_integer(), binary()}  Websocket frame.
This message informs the relevant process that the server sent the enclosed frame.
This message can only be sent on streams that were upgraded to the Websocket protocol.
Elements ConnPid The pid of the Gun connection process.</description>
    </item>
    
    <item>
      <title>gun_ws(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.1/manual/gun_ws/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.1/manual/gun_ws/</guid>
      <description>Name gun_ws - Websocket frame
Description {gun_ws, ConnPid, StreamRef, Frame} ConnPid :: pid() StreamRef :: reference() Frame :: close | {text | binary | close, binary()} | {close, non_neg_integer(), binary()}  Websocket frame.
This message informs the relevant process that the server sent the enclosed frame.
This message can only be sent on streams that were upgraded to the Websocket protocol.
Elements ConnPid The pid of the Gun connection process.</description>
    </item>
    
    <item>
      <title>gun_ws(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.2/manual/gun_ws/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.2/manual/gun_ws/</guid>
      <description>Name gun_ws - Websocket frame
Description {gun_ws, ConnPid, StreamRef, Frame} ConnPid :: pid() StreamRef :: reference() Frame :: close | {text | binary | close, binary()} | {close, non_neg_integer(), binary()}  Websocket frame.
This message informs the relevant process that the server sent the enclosed frame.
This message can only be sent on streams that were upgraded to the Websocket protocol.
Elements ConnPid The pid of the Gun connection process.</description>
    </item>
    
    <item>
      <title>gun_ws(3)</title>
      <link>https://ninenines.eu/docs/en/gun/1.3/manual/gun_ws/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/1.3/manual/gun_ws/</guid>
      <description>Name gun_ws - Websocket frame
Description {gun_ws, ConnPid, StreamRef, Frame} ConnPid :: pid() StreamRef :: reference() Frame :: close | {text | binary | close, binary()} | {close, non_neg_integer(), binary()}  Websocket frame.
This message informs the relevant process that the server sent the enclosed frame.
This message can only be sent on streams that were upgraded to the Websocket protocol.
Elements ConnPid The pid of the Gun connection process.</description>
    </item>
    
    <item>
      <title>gun_ws(3)</title>
      <link>https://ninenines.eu/docs/en/gun/2.0/manual/gun_ws/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/gun/2.0/manual/gun_ws/</guid>
      <description>Name gun_ws - Websocket frame
Description {gun_ws, ConnPid, StreamRef, Frame} ConnPid :: pid() StreamRef :: reference() Frame :: close | ping | pong | {text | binary | close, binary()} | {close, non_neg_integer(), binary()} | {ping | pong, binary()}  Websocket frame.
This message informs the relevant process that the server sent the enclosed frame.
This message can only be sent on streams that were upgraded to the Websocket protocol.</description>
    </item>
    
    <item>
      <title>HTTP status codes(7)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.2/manual/http_status_codes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.2/manual/http_status_codes/</guid>
      <description>Name HTTP status codes - status codes used by Cowboy
Description This chapter aims to list all HTTP status codes that Cowboy may return, with details on the reasons why. The list given here only includes the replies that Cowboy sends, not user replies.
100 Continue When the client sends an expect: 100-continue header, Cowboy automatically sends a this status code before trying to read the request body. This behavior can be disabled using the appropriate body option.</description>
    </item>
    
    <item>
      <title>HTTP status codes(7)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.3/manual/http_status_codes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.3/manual/http_status_codes/</guid>
      <description>Name HTTP status codes - status codes used by Cowboy
Description This chapter aims to list all HTTP status codes that Cowboy may return, with details on the reasons why. The list given here only includes the replies that Cowboy sends, not user replies.
100 Continue When the client sends an expect: 100-continue header, Cowboy automatically sends a this status code before trying to read the request body. This behavior can be disabled using the appropriate body option.</description>
    </item>
    
    <item>
      <title>HTTP status codes(7)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.4/manual/http_status_codes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.4/manual/http_status_codes/</guid>
      <description>Name HTTP status codes - status codes used by Cowboy
Description This chapter aims to list all HTTP status codes that Cowboy may return, with details on the reasons why. The list given here only includes the replies that Cowboy sends, not user replies.
100 Continue When the client sends an expect: 100-continue header, Cowboy automatically sends a this status code before trying to read the request body. This behavior can be disabled using the appropriate body option.</description>
    </item>
    
    <item>
      <title>HTTP status codes(7)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.5/manual/http_status_codes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.5/manual/http_status_codes/</guid>
      <description>Name HTTP status codes - status codes used by Cowboy
Description This chapter aims to list all HTTP status codes that Cowboy may return, with details on the reasons why. The list given here only includes the replies that Cowboy sends, not user replies.
100 Continue When the client sends an expect: 100-continue header, Cowboy automatically sends a this status code before trying to read the request body. This behavior can be disabled using the appropriate body option.</description>
    </item>
    
    <item>
      <title>HTTP status codes(7)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.6/manual/http_status_codes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.6/manual/http_status_codes/</guid>
      <description>Name HTTP status codes - status codes used by Cowboy
Description This chapter aims to list all HTTP status codes that Cowboy may return, with details on the reasons why. The list given here only includes the replies that Cowboy sends, not user replies.
100 Continue When the client sends an expect: 100-continue header, Cowboy automatically sends a this status code before trying to read the request body. This behavior can be disabled using the appropriate body option.</description>
    </item>
    
    <item>
      <title>HTTP status codes(7)</title>
      <link>https://ninenines.eu/docs/en/cowboy/2.7/manual/http_status_codes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/cowboy/2.7/manual/http_status_codes/</guid>
      <description>Name HTTP status codes - status codes used by Cowboy
Description This chapter aims to list all HTTP status codes that Cowboy may return, with details on the reasons why. The list given here only includes the replies that Cowboy sends, not user replies.
100 Continue When the client sends an expect: 100-continue header, Cowboy automatically sends a this status code before trying to read the request body. This behavior can be disabled using the appropriate body option.</description>
    </item>
    
    <item>
      <title>Ranch Function Reference</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/manual/</guid>
      <description>ranch(7)  ranch(3)  ranch_protocol(3)  ranch_ssl(3)  ranch_tcp(3)  ranch_transport(3)   </description>
    </item>
    
    <item>
      <title>Ranch Function Reference</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/manual/</guid>
      <description>ranch(7)  ranch(3)  ranch_protocol(3)  ranch_ssl(3)  ranch_tcp(3)  ranch_transport(3)   </description>
    </item>
    
    <item>
      <title>Ranch Function Reference</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/</guid>
      <description>Name ranch - Socket acceptor pool for TCP protocols
Description Ranch is a socket acceptor pool for TCP protocols.
Ranch manages listeners which are a set of processes that accept and manage connections. The connection&amp;apos;s transport and protocol modules are configured per listener. Listeners can be inspected and reconfigured without interruptions in service.
Modules Functions:
ranch(3) - Socket acceptor pool   Transports:
ranch_ssl(3) - SSL transport  ranch_tcp(3) - TLS transport   Behaviors:</description>
    </item>
    
    <item>
      <title>Ranch Function Reference</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/</guid>
      <description>Name ranch - Socket acceptor pool for TCP protocols
Description Ranch is a socket acceptor pool for TCP protocols.
Ranch manages listeners which are a set of processes that accept and manage connections. The connection&amp;apos;s transport and protocol modules are configured per listener. Listeners can be inspected and reconfigured without interruptions in service.
Modules Functions:
ranch(3) - Socket acceptor pool  ranch_proxy_header(3) - PROXY protocol   Transports:
ranch_ssl(3) - SSL transport  ranch_tcp(3) - TCP transport   Behaviors:</description>
    </item>
    
    <item>
      <title>Ranch Function Reference</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/</guid>
      <description>Name ranch - Socket acceptor pool for TCP protocols
Description Ranch is a socket acceptor pool for TCP protocols.
Ranch manages listeners which are a set of processes that accept and manage connections. The connection&amp;apos;s transport and protocol modules are configured per listener. Listeners can be inspected and reconfigured without interruptions in service.
Modules Functions:
ranch(3) - Socket acceptor pool  ranch_proxy_header(3) - PROXY protocol   Transports:
ranch_ssl(3) - SSL transport  ranch_tcp(3) - TCP transport   Behaviors:</description>
    </item>
    
    <item>
      <title>Ranch User Guide</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/guide/</guid>
      <description>Introduction  Listeners  Transports  Protocols  Embedded mode  Writing parsers  SSL client authentication  Internals   </description>
    </item>
    
    <item>
      <title>Ranch User Guide</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/guide/</guid>
      <description>Introduction  Listeners  Transports  Protocols  Embedded mode  Writing parsers  SSL client authentication  Internals   </description>
    </item>
    
    <item>
      <title>Ranch User Guide</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/guide/</guid>
      <description>Interface Introduction  Listeners  Transports  Protocols  Embedded mode   How to Writing parsers  SSL client authentication   Advanced Internals   Additional information Upcoming changes in Ranch 2.0  Changes since Ranch 1.6  Migrating from Ranch 1.5 to 1.6  Migrating from Ranch 1.x   </description>
    </item>
    
    <item>
      <title>Ranch User Guide</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/guide/</guid>
      <description>Interface Introduction  Listeners  Transports  Protocols  Embedded mode   How to Writing parsers  SSL client authentication   Advanced Internals   Additional information Upcoming changes in Ranch 2.0  Changes since Ranch 1.7  Migrating from Ranch 1.6 to 1.7  Migrating from Ranch 1.5 to 1.6  Migrating from Ranch 1.x   </description>
    </item>
    
    <item>
      <title>Ranch User Guide</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/guide/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/guide/</guid>
      <description>Interface Introduction  Listeners  Transports  Protocols  Embedded mode   How to Writing parsers  SSL client authentication  Connection draining   Advanced Internals   Additional information Migrating from Ranch 1.7 to 2.0  Migrating from Ranch 1.6 to 1.7  Migrating from Ranch 1.5 to 1.6  Migrating from Ranch 1.x   </description>
    </item>
    
    <item>
      <title>ranch(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/manual/ranch/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/manual/ranch/</guid>
      <description>Name ranch - socket acceptor pool
Description The ranch module provides functions for starting and manipulating Ranch listeners.
Types max_conns() = non_neg_integer() | infinity Maximum number of connections allowed on this listener.
This is a soft limit. The actual number of connections might be slightly above the limit due to concurrency when accepting new connections. Some connections may also be removed from this count explicitly by the user code.
opt() opt() = {ack_timeout, timeout()} | {connection_type, worker | supervisor} | {max_connections, max_conns()} | {num_acceptors, pos_integer()} | {shutdown, timeout() | brutal_kill} | {socket, any()}  Ranch-specific transport options.</description>
    </item>
    
    <item>
      <title>ranch(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/manual/ranch/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/manual/ranch/</guid>
      <description>Name ranch - socket acceptor pool
Description The ranch module provides functions for starting and manipulating Ranch listeners.
Types max_conns() = non_neg_integer() | infinity Maximum number of connections allowed on this listener.
This is a soft limit. The actual number of connections might be slightly above the limit due to concurrency when accepting new connections. Some connections may also be removed from this count explicitly by the user code.
opt() opt() = {ack_timeout, timeout()} | {connection_type, worker | supervisor} | {max_connections, max_conns()} | {num_acceptors, pos_integer()} | {shutdown, timeout() | brutal_kill} | {socket, any()}  Ranch-specific transport options.</description>
    </item>
    
    <item>
      <title>ranch(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch/</guid>
      <description>Name ranch - Socket acceptor pool
Description The module ranch provides functions for starting and manipulating Ranch listeners.
Exports Start/stop:
ranch:start_listener(3) - Start a listener  ranch:stop_listener(3) - Stop a listener  ranch:child_spec(3) - Build child specifications for a new listener   Suspend/resume:
ranch:suspend_listener(3) - Suspend a running listener  ranch:resume_listener(3) - Resume a suspended listener  ranch:get_status(3) - Get a listener&amp;apos;s running state   Connections:
ranch:accept_ack(3) - Deprecated in favor of ranch:handshake(3)  ranch:handshake(3) - Perform the transport handshake  ranch:remove_connection(3) - Remove connection from the count   Options:</description>
    </item>
    
    <item>
      <title>ranch(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch/</guid>
      <description>Name ranch - Socket acceptor pool
Description The module ranch provides functions for starting and manipulating Ranch listeners.
Exports Start/stop:
ranch:start_listener(3) - Start a listener  ranch:stop_listener(3) - Stop a listener  ranch:child_spec(3) - Build child specifications for a new listener   Suspend/resume:
ranch:suspend_listener(3) - Suspend a running listener  ranch:resume_listener(3) - Resume a suspended listener  ranch:get_status(3) - Get a listener&amp;apos;s running state   Connections:
ranch:accept_ack(3) - Deprecated in favor of ranch:handshake(3)  ranch:handshake(3) - Perform the transport handshake  ranch:recv_proxy_header(3) - Receive the PROXY protocol header  ranch:remove_connection(3) - Remove connection from the count   Options:</description>
    </item>
    
    <item>
      <title>ranch(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch/</guid>
      <description>Name ranch - Socket acceptor pool
Description The module ranch provides functions for starting and manipulating Ranch listeners.
Exports Start/stop:
ranch:start_listener(3) - Start a listener  ranch:stop_listener(3) - Stop a listener  ranch:child_spec(3) - Build child specifications for a new listener   Suspend/resume:
ranch:suspend_listener(3) - Suspend a running listener  ranch:resume_listener(3) - Resume a suspended listener  ranch:get_status(3) - Get a listener&amp;apos;s running state   Connections:
ranch:handshake(3) - Perform the transport handshake  ranch:handshake_continue(3) - Resume the paused transport handshake  ranch:handshake_cancel(3) - Cancel the paused transport handshake  ranch:recv_proxy_header(3) - Receive the PROXY protocol header  ranch:remove_connection(3) - Remove connection from the count   Options:</description>
    </item>
    
    <item>
      <title>ranch(7)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/manual/ranch_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/manual/ranch_app/</guid>
      <description>Name ranch - Socket acceptor pool for TCP protocols.
Dependencies The ranch application depends on the ssl application to start. It is used for handling secure connections, when the transport is ranch_ssl. It can be disabled if SSL is not used.
Environment The ranch application defines one application environment configuration parameter.
profile (false) When enabled, Ranch will start eprof profiling automatically.
  You can use the ranch_app:profile_output/0 function to stop profiling and output the results to the files procs.</description>
    </item>
    
    <item>
      <title>ranch(7)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/manual/ranch_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/manual/ranch_app/</guid>
      <description>Name ranch - Socket acceptor pool for TCP protocols.
Dependencies The ranch application depends on the ssl application to start. It is used for handling secure connections, when the transport is ranch_ssl. It can be disabled if SSL is not used.
Environment The ranch application defines one application environment configuration parameter.
profile (false) When enabled, Ranch will start eprof profiling automatically.
  You can use the ranch_app:profile_output/0 function to stop profiling and output the results to the files procs.</description>
    </item>
    
    <item>
      <title>ranch(7)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch_app/</guid>
      <description>Name ranch - Socket acceptor pool for TCP protocols
Description Ranch is a socket acceptor pool for TCP protocols.
Ranch manages listeners which are a set of processes that accept and manage connections. The connection&amp;apos;s transport and protocol modules are configured per listener. Listeners can be inspected and reconfigured without interruptions in service.
Modules Functions:
ranch(3) - Socket acceptor pool   Transports:
ranch_ssl(3) - SSL transport  ranch_tcp(3) - TLS transport   Behaviors:</description>
    </item>
    
    <item>
      <title>ranch(7)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_app/</guid>
      <description>Name ranch - Socket acceptor pool for TCP protocols
Description Ranch is a socket acceptor pool for TCP protocols.
Ranch manages listeners which are a set of processes that accept and manage connections. The connection&amp;apos;s transport and protocol modules are configured per listener. Listeners can be inspected and reconfigured without interruptions in service.
Modules Functions:
ranch(3) - Socket acceptor pool  ranch_proxy_header(3) - PROXY protocol   Transports:
ranch_ssl(3) - SSL transport  ranch_tcp(3) - TCP transport   Behaviors:</description>
    </item>
    
    <item>
      <title>ranch(7)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_app/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_app/</guid>
      <description>Name ranch - Socket acceptor pool for TCP protocols
Description Ranch is a socket acceptor pool for TCP protocols.
Ranch manages listeners which are a set of processes that accept and manage connections. The connection&amp;apos;s transport and protocol modules are configured per listener. Listeners can be inspected and reconfigured without interruptions in service.
Modules Functions:
ranch(3) - Socket acceptor pool  ranch_proxy_header(3) - PROXY protocol   Transports:
ranch_ssl(3) - SSL transport  ranch_tcp(3) - TCP transport   Behaviors:</description>
    </item>
    
    <item>
      <title>ranch:child_spec(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.child_spec/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.child_spec/</guid>
      <description>Name ranch:child_spec - Build child specifications for a new listener
Description child_spec(Ref :: ranch_ref(), Transport :: module(), TransOpts :: ranch:opts(), Protocol :: module(), ProtoOpts :: any()) -&amp;gt; supervisor:child_spec()  Build child specifications for a new listener.
This function can be used to embed a listener directly in an application&amp;apos;s supervision tree.
Arguments Ref The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the configuration.</description>
    </item>
    
    <item>
      <title>ranch:child_spec(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.child_spec/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.child_spec/</guid>
      <description>Name ranch:child_spec - Build child specifications for a new listener
Description child_spec(Ref :: ranch_ref(), Transport :: module(), TransOpts :: ranch:opts(), Protocol :: module(), ProtoOpts :: any()) -&amp;gt; supervisor:child_spec()  Build child specifications for a new listener.
This function can be used to embed a listener directly in an application&amp;apos;s supervision tree.
Arguments Ref The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the configuration.</description>
    </item>
    
    <item>
      <title>ranch:child_spec(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.child_spec/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.child_spec/</guid>
      <description>Name ranch:child_spec - Build child specifications for a new listener
Description child_spec(Ref :: ranch_ref(), Transport :: module(), TransOpts :: ranch:opts(), Protocol :: module(), ProtoOpts :: any()) -&amp;gt; supervisor:child_spec()  Build child specifications for a new listener which can be embedded directly in an application&amp;apos;s supervision tree.
The actual listener is placed under a supervisor which monitors ranch_server via a proxy process and will restart the listener if ranch_server crashes.
Arguments Ref The listener name is used to refer to this listener in future calls, for example when updating the configuration.</description>
    </item>
    
    <item>
      <title>ranch:get_addr(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.get_addr/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.get_addr/</guid>
      <description>Name ranch:get_addr - Get the listening port and IP
Description get_addr(Ref :: ranch:ref()) -&amp;gt; {IP :: inet:ip_address(), Port :: inet:port_number()}  Get the listening port and IP.
Arguments Ref The listener name.
  Return value The address of the listener is returned as a tuple.
The IP address is the IP of the network interface the socket is bound to.
Examples Get the listening port and IP {IP, Port} = ranch:get_addr(example).</description>
    </item>
    
    <item>
      <title>ranch:get_addr(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.get_addr/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.get_addr/</guid>
      <description>Name ranch:get_addr - Get the listening port and IP
Description get_addr(Ref :: ranch:ref()) -&amp;gt; {IP :: inet:ip_address(), Port :: inet:port_number()}  Get the listening port and IP.
Arguments Ref The listener name.
  Return value The address of the listener is returned as a tuple.
The IP address is the IP of the network interface the socket is bound to.
Examples Get the listening port and IP {IP, Port} = ranch:get_addr(example).</description>
    </item>
    
    <item>
      <title>ranch:get_addr(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.get_addr/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.get_addr/</guid>
      <description>Name ranch:get_addr - Get the listening address
Description get_addr(Ref :: ranch:ref()) -&amp;gt; {IP :: inet:ip_address(), Port :: inet:port_number()} | {local, SocketFile :: binary()} | {undefined, undefined}  Get the listening address.
Arguments Ref The listener name.
  Return value The address of the listener is returned as a tuple of the form {IP, Port} when listening on a network interface, or {local, SocketFile} when listening on a UNIX Domain socket.</description>
    </item>
    
    <item>
      <title>ranch:get_max_connections(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.get_max_connections/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.get_max_connections/</guid>
      <description>Name ranch:get_max_connections - Get the max number of connections
Description get_max_connections(Ref :: ranch:ref()) -&amp;gt; MaxConns :: ranch:max_conns()  Get the max number of connections.
Arguments Ref The listener name.
  Return value The maximum number of connections is returned.
Examples Get the max number of connections MaxConns = ranch:get_max_connections(example).  See also ranch:get_protocol_options(3), ranch:get_transport_options(3), ranch:set_max_connections(3), ranch(3)</description>
    </item>
    
    <item>
      <title>ranch:get_max_connections(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.get_max_connections/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.get_max_connections/</guid>
      <description>Name ranch:get_max_connections - Get the max number of connections
Description get_max_connections(Ref :: ranch:ref()) -&amp;gt; MaxConns :: ranch:max_conns()  Get the max number of connections.
Arguments Ref The listener name.
  Return value The maximum number of connections is returned.
Examples Get the max number of connections MaxConns = ranch:get_max_connections(example).  See also ranch:get_protocol_options(3), ranch:get_transport_options(3), ranch:set_max_connections(3), ranch(3)</description>
    </item>
    
    <item>
      <title>ranch:get_max_connections(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.get_max_connections/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.get_max_connections/</guid>
      <description>Name ranch:get_max_connections - Get the max number of connections per connection supervisor
Description get_max_connections(Ref :: ranch:ref()) -&amp;gt; MaxConns :: ranch:max_conns()  Get the max number of connections per connection supervisor.
Arguments Ref The listener name.
  Return value The maximum number of connections per connection supervisor is returned.
Changelog 2.0: The maximum number of connections is now per connection supervisor.   Examples Get the max number of connections per connection supervisor MaxConns = ranch:get_max_connections(example).</description>
    </item>
    
    <item>
      <title>ranch:get_port(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.get_port/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.get_port/</guid>
      <description>Name ranch:get_port - Get the listening port
Description get_port(Ref :: ranch:ref()) -&amp;gt; Port :: inet:port_number()  Get the listening port.
This function is particularly useful to retrieve the listening port number when it was not provided in the options and was chosen randomly instead.
Arguments Ref The listener name.
  Return value The listening port is returned.
Examples Get the listening port Port = ranch:get_port(example).  See also ranch:start_listener(3), ranch:get_addr(3), ranch:info(3), ranch(3)</description>
    </item>
    
    <item>
      <title>ranch:get_port(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.get_port/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.get_port/</guid>
      <description>Name ranch:get_port - Get the listening port
Description get_port(Ref :: ranch:ref()) -&amp;gt; Port :: inet:port_number()  Get the listening port.
This function is particularly useful to retrieve the listening port number when it was not provided in the options and was chosen randomly instead.
Arguments Ref The listener name.
  Return value The listening port is returned.
Examples Get the listening port Port = ranch:get_port(example).  See also ranch:start_listener(3), ranch:get_addr(3), ranch:info(3), ranch(3)</description>
    </item>
    
    <item>
      <title>ranch:get_port(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.get_port/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.get_port/</guid>
      <description>Name ranch:get_port - Get the listening port
Description get_port(Ref :: ranch:ref()) -&amp;gt; Port :: inet:port_number() | undefined  Get the listening port.
This function is particularly useful to retrieve the listening port number when it was not provided in the options and was chosen randomly instead.
Arguments Ref The listener name.
  Return value The listening port is returned.
When the listener is suspended or using a UNIX Domain socket instead of a network interface, undefined will be returned.</description>
    </item>
    
    <item>
      <title>ranch:get_protocol_options(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.get_protocol_options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.get_protocol_options/</guid>
      <description>Name ranch:get_protocol_options - Get the current protocol options
Description get_protocol_options(Ref :: ranch:ref()) -&amp;gt; ProtoOpts :: any()  Get the current protocol options.
Arguments Ref The listener name.
  Return value The current protocol options are returned.
Examples Get the current protocol options ProtoOpts = ranch:get_protocol_options(example).  See also ranch:get_max_connections(3), ranch:get_transport_options(3), ranch:set_protocol_options(3), ranch(3)</description>
    </item>
    
    <item>
      <title>ranch:get_protocol_options(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.get_protocol_options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.get_protocol_options/</guid>
      <description>Name ranch:get_protocol_options - Get the current protocol options
Description get_protocol_options(Ref :: ranch:ref()) -&amp;gt; ProtoOpts :: any()  Get the current protocol options.
Arguments Ref The listener name.
  Return value The current protocol options are returned.
Examples Get the current protocol options ProtoOpts = ranch:get_protocol_options(example).  See also ranch:get_max_connections(3), ranch:get_transport_options(3), ranch:set_protocol_options(3), ranch(3)</description>
    </item>
    
    <item>
      <title>ranch:get_protocol_options(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.get_protocol_options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.get_protocol_options/</guid>
      <description>Name ranch:get_protocol_options - Get the current protocol options
Description get_protocol_options(Ref :: ranch:ref()) -&amp;gt; ProtoOpts :: any()  Get the current protocol options.
Arguments Ref The listener name.
  Return value The current protocol options are returned.
Examples Get the current protocol options ProtoOpts = ranch:get_protocol_options(example).  See also ranch:get_max_connections(3), ranch:get_transport_options(3), ranch:set_protocol_options(3), ranch(3)</description>
    </item>
    
    <item>
      <title>ranch:get_status(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.get_status/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.get_status/</guid>
      <description>Name ranch:get_status - Get a listener&amp;apos;s running state
Description get_status(Ref :: ranch_ref()) -&amp;gt; running | suspended  Get a listener&amp;apos;s running state.
Arguments Ref The listener name.
  Return value An atom is returned indicating the running status of the listener.
Changelog 1.6: Function introduced.   Examples Get a listener&amp;apos;s running state ranch:get_status(example).  See also ranch:start_listener(3), ranch:stop_listener(3), ranch:suspend_listener(3), ranch:resume_listener(3), ranch:set_transport_options(3), ranch:wait_for_connections(3), ranch(3)</description>
    </item>
    
    <item>
      <title>ranch:get_status(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.get_status/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.get_status/</guid>
      <description>Name ranch:get_status - Get a listener&amp;apos;s running state
Description get_status(Ref :: ranch_ref()) -&amp;gt; running | suspended  Get a listener&amp;apos;s running state.
Arguments Ref The listener name.
  Return value An atom is returned indicating the running status of the listener.
Changelog 1.6: Function introduced.   Examples Get a listener&amp;apos;s running state ranch:get_status(example).  See also ranch:start_listener(3), ranch:stop_listener(3), ranch:suspend_listener(3), ranch:resume_listener(3), ranch:set_transport_options(3), ranch:wait_for_connections(3), ranch(3)</description>
    </item>
    
    <item>
      <title>ranch:get_status(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.get_status/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.get_status/</guid>
      <description>Name ranch:get_status - Get a listener&amp;apos;s running state
Description get_status(Ref :: ranch_ref()) -&amp;gt; running | suspended  Get a listener&amp;apos;s running state.
Arguments Ref The listener name.
  Return value An atom is returned indicating the running status of the listener.
Changelog 1.6: Function introduced.   Examples Get a listener&amp;apos;s running state ranch:get_status(example).  See also ranch:start_listener(3), ranch:stop_listener(3), ranch:suspend_listener(3), ranch:resume_listener(3), ranch:set_transport_options(3), ranch:wait_for_connections(3), ranch(3)</description>
    </item>
    
    <item>
      <title>ranch:get_transport_options(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.get_transport_options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.get_transport_options/</guid>
      <description>Name ranch:get_transport_options - Get the current transport options
Description get_transport_options(Ref :: ranch:ref()) -&amp;gt; TransOpts :: any()  Get the current transport options.
Arguments Ref The listener name.
  Return value The current transport options are returned.
Examples Get the current transport options TransOpts = ranch:get_transport_options(example).  See also ranch:get_max_connections(3), ranch:get_protocol_options(3), ranch:set_transport_options(3), ranch(3)</description>
    </item>
    
    <item>
      <title>ranch:get_transport_options(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.get_transport_options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.get_transport_options/</guid>
      <description>Name ranch:get_transport_options - Get the current transport options
Description get_transport_options(Ref :: ranch:ref()) -&amp;gt; TransOpts :: any()  Get the current transport options.
Arguments Ref The listener name.
  Return value The current transport options are returned.
Examples Get the current transport options TransOpts = ranch:get_transport_options(example).  See also ranch:get_max_connections(3), ranch:get_protocol_options(3), ranch:set_transport_options(3), ranch(3)</description>
    </item>
    
    <item>
      <title>ranch:get_transport_options(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.get_transport_options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.get_transport_options/</guid>
      <description>Name ranch:get_transport_options - Get the current transport options
Description get_transport_options(Ref :: ranch:ref()) -&amp;gt; TransOpts :: any()  Get the current transport options.
Arguments Ref The listener name.
  Return value The current transport options are returned.
Examples Get the current transport options TransOpts = ranch:get_transport_options(example).  See also ranch:get_max_connections(3), ranch:get_protocol_options(3), ranch:set_transport_options(3), ranch(3)</description>
    </item>
    
    <item>
      <title>ranch:handshake(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.handshake/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.handshake/</guid>
      <description>Name ranch:handshake - Perform the transport handshake
Description handshake(Ref) -&amp;gt; handshake(Ref, []) handshake(Ref, Opts) -&amp;gt; {ok, Socket} Ref :: ranch:ref() Opts :: any() Socket :: any()  Perform the transport handshake.
This function must be called by the protocol process in order to retrieve the socket for the connection. Ranch performs the handshake necessary to give control of the socket to this process and also does the transport handshake, for example setting up the TLS connection.</description>
    </item>
    
    <item>
      <title>ranch:handshake(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.handshake/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.handshake/</guid>
      <description>Name ranch:handshake - Perform the transport handshake
Description handshake(Ref) -&amp;gt; handshake(Ref, []) handshake(Ref, Opts) -&amp;gt; {ok, Socket} Ref :: ranch:ref() Opts :: any() Socket :: any()  Perform the transport handshake.
This function must be called by the protocol process in order to retrieve the socket for the connection. Ranch performs the handshake necessary to give control of the socket to this process and also does the transport handshake, for example setting up the TLS connection.</description>
    </item>
    
    <item>
      <title>ranch:handshake(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.handshake/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.handshake/</guid>
      <description>Name ranch:handshake - Perform the transport handshake
Description handshake(Ref) -&amp;gt; {ok, Socket} | {continue, Info} handshake(Ref, Opts) -&amp;gt; {ok, Socket} | {continue, Info} Ref :: ranch:ref() Opts :: any() Socket :: any() Info :: any()  Perform the transport handshake.
This function must be called by the protocol process in order to retrieve the socket for the connection. Ranch performs the handshake necessary to give control of the socket to this process and also does the transport handshake, for example setting up the TLS connection.</description>
    </item>
    
    <item>
      <title>ranch:handshake_cancel(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.handshake_cancel/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.handshake_cancel/</guid>
      <description>Name ranch:handshake_cancel - Cancel the paused transport handshake
Description handshake_cancel(Ref :: ranch:ref()) -&amp;gt; ok  Cancel the paused transport handshake.
This function may be called by the protocol process to cancel a paused handshake.
Arguments Ref The listener name.
Allowed options depend on the transport module.
  Return value The return value depends on the transport module.
Changelog 2.0: Function introduced.   Examples Cancel a paused transport handshake start_link(Ref, Transport, Opts) -&amp;gt; Pid = proc_lib:spawn_link(?</description>
    </item>
    
    <item>
      <title>ranch:handshake_continue(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.handshake_continue/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.handshake_continue/</guid>
      <description>Name ranch:handshake_continue - Resume the paused transport handshake
Description handshake_continue(Ref) -&amp;gt; {ok, Socket} handshake_continue(Ref, Opts) -&amp;gt; {ok, Socket} Ref :: ranch:ref() Opts :: any() Socket :: any()  Resume the paused transport handshake.
This function must be called by the protocol process in order to resume a paused handshake.
Arguments Ref The listener name.
 Opts Transport handshake options.
Allowed options depend on the transport module.
  Return value An ok tuple is returned containing the socket for the connection.</description>
    </item>
    
    <item>
      <title>ranch:info(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.info/</guid>
      <description>Name ranch:info - Overview of Ranch listeners
Description info() -&amp;gt; [{Ref, Info}] info(Ref) -&amp;gt; Info Info :: [{Key :: atom(), Value :: any()}]  Overview of Ranch listeners.
Arguments Ref The listener name.
  Return value Returns detailed information about one or all Ranch listeners. The following keys are returned:
pid Pid of the listener&amp;apos;s top-level supervisor.
 status Listener status, either running or suspended.
 ip Interface Ranch listens on.</description>
    </item>
    
    <item>
      <title>ranch:info(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.info/</guid>
      <description>Name ranch:info - Overview of Ranch listeners
Description info() -&amp;gt; [{Ref, Info}] info(Ref) -&amp;gt; Info Info :: [{Key :: atom(), Value :: any()}]  Overview of Ranch listeners.
Arguments Ref The listener name.
  Return value Returns detailed information about one or all Ranch listeners. The following keys are returned:
pid Pid of the listener&amp;apos;s top-level supervisor.
 status Listener status, either running or suspended.
 ip Interface Ranch listens on.</description>
    </item>
    
    <item>
      <title>ranch:info(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.info/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.info/</guid>
      <description>Name ranch:info - Overview of Ranch listeners
Description info() -&amp;gt; #{Ref := Info} info(Ref) -&amp;gt; Info Info :: #{Key :: atom() := Value :: any()}  Overview of Ranch listeners.
Arguments Ref The listener name.
  Return value Returns detailed information about one or all Ranch listeners. The following keys are returned:
pid Pid of the listener&amp;apos;s top-level supervisor.
 status Listener status, either running or suspended.
 ip Interface Ranch listens on.</description>
    </item>
    
    <item>
      <title>ranch:procs(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.procs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.procs/</guid>
      <description>Name ranch:procs - Retrieve pids from a listener
Description procs(Ref :: ranch:ref(), Type :: acceptors | connections) -&amp;gt; Pids :: [pid()]  Retrieve pids from a listener.
Arguments Ref The listener name.
 Type The type of process that will be returned.
  Return value A list of pids is returned.
Examples Get the pids of the acceptor processes Pids = ranch:procs(acceptors).  Get the pids of the connection processes Pids = ranch:procs(connections).</description>
    </item>
    
    <item>
      <title>ranch:procs(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.procs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.procs/</guid>
      <description>Name ranch:procs - Retrieve pids from a listener
Description procs(Ref :: ranch:ref(), Type :: acceptors | connections) -&amp;gt; Pids :: [pid()]  Retrieve pids from a listener.
Arguments Ref The listener name.
 Type The type of process that will be returned.
  Return value A list of pids is returned.
Examples Get the pids of the acceptor processes Pids = ranch:procs(acceptors).  Get the pids of the connection processes Pids = ranch:procs(connections).</description>
    </item>
    
    <item>
      <title>ranch:procs(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.procs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.procs/</guid>
      <description>Name ranch:procs - Retrieve pids from a listener
Description procs(Ref :: ranch:ref(), Type :: acceptors | connections) -&amp;gt; Pids :: [pid()]  Retrieve pids from a listener.
Arguments Ref The listener name.
 Type The type of process that will be returned.
  Return value A list of pids is returned.
Examples Get the pids of the acceptor processes Pids = ranch:procs(acceptors).  Get the pids of the connection processes Pids = ranch:procs(connections).</description>
    </item>
    
    <item>
      <title>ranch:recv_proxy_header(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.recv_proxy_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.recv_proxy_header/</guid>
      <description>Name ranch:recv_proxy_header - Receive the PROXY protocol header
Description recv_proxy_header(ranch:ref(), timeout()) -&amp;gt; {ok, ranch_proxy_header:proxy_info()} | {error, Reason :: atom()} | {error, protocol_error, HumanReadable :: atom()}  Receive the PROXY protocol header.
This function must be called before ranch:handshake/1,2 on newly accepted connections to read and parse the PROXY protocol header, if any.
Arguments Ref The listener name.
 Timeout Receive timeout in milliseconds.
  Return value An ok tuple is returned containing PROXY header information on success.</description>
    </item>
    
    <item>
      <title>ranch:recv_proxy_header(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.recv_proxy_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.recv_proxy_header/</guid>
      <description>Name ranch:recv_proxy_header - Receive the PROXY protocol header
Description recv_proxy_header(ranch:ref(), timeout()) -&amp;gt; {ok, ranch_proxy_header:proxy_info()} | {error, Reason :: atom()} | {error, protocol_error, HumanReadable :: atom()}  Receive the PROXY protocol header.
This function must be called before ranch:handshake/1,2 on newly accepted connections to read and parse the PROXY protocol header, if any.
Arguments Ref The listener name.
 Timeout Receive timeout in milliseconds.
  Return value An ok tuple is returned containing PROXY header information on success.</description>
    </item>
    
    <item>
      <title>ranch:remove_connection(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.remove_connection/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.remove_connection/</guid>
      <description>Name ranch:remove_connection - Remove connection from the count
Description remove_connection(Ref :: ranch:ref()) -&amp;gt; ok  Remove connection from the count.
This connection will no longer be included in the count when limiting the number of connections. This can be useful in a mixed environment where some connections are active and others are passive. Passive connections spend most of their time idling and are not consuming much resources.
This function may only be called from a connection process.</description>
    </item>
    
    <item>
      <title>ranch:remove_connection(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.remove_connection/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.remove_connection/</guid>
      <description>Name ranch:remove_connection - Remove connection from the count
Description remove_connection(Ref :: ranch:ref()) -&amp;gt; ok  Remove connection from the count.
This connection will no longer be included in the count when limiting the number of connections. This can be useful in a mixed environment where some connections are active and others are passive. Passive connections spend most of their time idling and are not consuming much resources.
This function may only be called from a connection process.</description>
    </item>
    
    <item>
      <title>ranch:remove_connection(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.remove_connection/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.remove_connection/</guid>
      <description>Name ranch:remove_connection - Remove connection from the count
Description remove_connection(Ref :: ranch:ref()) -&amp;gt; ok  Remove connection from the count.
This connection will no longer be included in the count when limiting the number of connections. This can be useful in a mixed environment where some connections are active and others are passive. Passive connections spend most of their time idling and are not consuming much resources.
This function may only be called from a connection process.</description>
    </item>
    
    <item>
      <title>ranch:resume_listener(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.resume_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.resume_listener/</guid>
      <description>Name ranch:resume_listener - Resume a suspended listener
Description resume_listener(Ref :: ranch_ref()) -&amp;gt; ok | {error, any()}  Resume a suspended listener.
Ranch will start listening for and accepting connections again. The function ranch:set_transport_options(3) can be used to change the transport options before resuming the listener.
Nothing is done when the listener is already running.
Arguments Ref The listener name.
  Return value The atom ok is returned on success.</description>
    </item>
    
    <item>
      <title>ranch:resume_listener(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.resume_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.resume_listener/</guid>
      <description>Name ranch:resume_listener - Resume a suspended listener
Description resume_listener(Ref :: ranch_ref()) -&amp;gt; ok | {error, any()}  Resume a suspended listener.
Ranch will start listening for and accepting connections again. The function ranch:set_transport_options(3) can be used to change the transport options before resuming the listener.
Nothing is done when the listener is already running.
Arguments Ref The listener name.
  Return value The atom ok is returned on success.</description>
    </item>
    
    <item>
      <title>ranch:resume_listener(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.resume_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.resume_listener/</guid>
      <description>Name ranch:resume_listener - Resume a suspended listener
Description resume_listener(Ref :: ranch_ref()) -&amp;gt; ok | {error, any()}  Resume a suspended listener.
Ranch will start listening for and accepting connections again. The function ranch:set_transport_options(3) can be used to change the transport options before resuming the listener.
Nothing is done when the listener is already running.
Arguments Ref The listener name.
  Return value The atom ok is returned on success.</description>
    </item>
    
    <item>
      <title>ranch:set_max_connections(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.set_max_connections/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.set_max_connections/</guid>
      <description>Name ranch:set_max_connections - Set the max number of connections
Description set_max_connections(Ref :: ranch:ref(), MaxConns :: ranch:max_conns()) -&amp;gt; ok  Set the max number of connections.
The change will be applied immediately. If the new value is smaller than the previous one, Ranch will wait for the extra connections to terminate and will not accept new connections until the number of connections goes below the limit.
Arguments Ref The listener name.</description>
    </item>
    
    <item>
      <title>ranch:set_max_connections(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.set_max_connections/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.set_max_connections/</guid>
      <description>Name ranch:set_max_connections - Set the max number of connections
Description set_max_connections(Ref :: ranch:ref(), MaxConns :: ranch:max_conns()) -&amp;gt; ok  Set the max number of connections.
The change will be applied immediately. If the new value is smaller than the previous one, Ranch will wait for the extra connections to terminate and will not accept new connections until the number of connections goes below the limit.
Arguments Ref The listener name.</description>
    </item>
    
    <item>
      <title>ranch:set_max_connections(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.set_max_connections/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.set_max_connections/</guid>
      <description>Name ranch:set_max_connections - Set the max number of connections per connection supervisor
Description set_max_connections(Ref :: ranch:ref(), MaxConns :: ranch:max_conns()) -&amp;gt; ok  Set the max number of connections per connection supervisor.
The change will be applied immediately. If the new value is smaller than the previous one, Ranch will wait for the extra connections to terminate and will not accept new connections until the number of connections goes below the limit.</description>
    </item>
    
    <item>
      <title>ranch:set_protocol_options(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.set_protocol_options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.set_protocol_options/</guid>
      <description>Name ranch:set_protocol_options - Set the protocol options
Description set_protocol_options(Ref :: ranch:ref(), ProtoOpts :: any()) -&amp;gt; ok  Set the protocol options.
The change will be applied immediately for all new connections. Old connections will not receive the new options.
Arguments Ref The listener name.
 ProtoOpts The new protocol options.
  Return value The atom ok is always returned. It can be safely ignored.
Examples Set the protocol options ranch:set_protocol_options(example, ProtoOpts).</description>
    </item>
    
    <item>
      <title>ranch:set_protocol_options(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.set_protocol_options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.set_protocol_options/</guid>
      <description>Name ranch:set_protocol_options - Set the protocol options
Description set_protocol_options(Ref :: ranch:ref(), ProtoOpts :: any()) -&amp;gt; ok  Set the protocol options.
The change will be applied immediately for all new connections. Old connections will not receive the new options.
Arguments Ref The listener name.
 ProtoOpts The new protocol options.
  Return value The atom ok is always returned. It can be safely ignored.
Examples Set the protocol options ranch:set_protocol_options(example, ProtoOpts).</description>
    </item>
    
    <item>
      <title>ranch:set_protocol_options(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.set_protocol_options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.set_protocol_options/</guid>
      <description>Name ranch:set_protocol_options - Set the protocol options
Description set_protocol_options(Ref :: ranch:ref(), ProtoOpts :: any()) -&amp;gt; ok  Set the protocol options.
The change will be applied immediately for all new connections. Old connections will not receive the new options.
Arguments Ref The listener name.
 ProtoOpts The new protocol options.
  Return value The atom ok is always returned. It can be safely ignored.
Examples Set the protocol options ranch:set_protocol_options(example, ProtoOpts).</description>
    </item>
    
    <item>
      <title>ranch:set_transport_options(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.set_transport_options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.set_transport_options/</guid>
      <description>Name ranch:set_transport_options - Set the transport options
Description set_transport_options(Ref :: ranch:ref(), TransOpts :: any()) -&amp;gt; ok | {error, running}  Set the transport options.
The listener must be suspended for this call to succeed. If the listener is running, {error, running} will be returned.
The change will take effect when the listener resumes.
Arguments Ref The listener name.
 TransOpts The new transport options.
  Return value The atom ok is always returned.</description>
    </item>
    
    <item>
      <title>ranch:set_transport_options(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.set_transport_options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.set_transport_options/</guid>
      <description>Name ranch:set_transport_options - Set the transport options
Description set_transport_options(Ref :: ranch:ref(), TransOpts :: any()) -&amp;gt; ok | {error, running}  Set the transport options.
The listener must be suspended for this call to succeed. If the listener is running, {error, running} will be returned.
The change will take effect when the listener resumes.
Arguments Ref The listener name.
 TransOpts The new transport options.
  Return value The atom ok is always returned.</description>
    </item>
    
    <item>
      <title>ranch:set_transport_options(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.set_transport_options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.set_transport_options/</guid>
      <description>Name ranch:set_transport_options - Set the transport options
Description set_transport_options(Ref :: ranch:ref(), TransOpts :: ranch:opts()) -&amp;gt; ok | {error, Reason :: term()}  Set the transport options.
Changes to the following options will take effect...
immediately: max_connections  handshake_timeout  shutdown    only after the listener has been suspended and resumed: num_acceptors  num_listen_sockets  socket_opts    only when the entire listener is restarted: connection_type  num_conns_sups  logger     Arguments Ref The listener name.</description>
    </item>
    
    <item>
      <title>ranch:start_listener(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.start_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.start_listener/</guid>
      <description>Name ranch:start_listener - Start a listener
Description start_listener(Ref :: ranch_ref(), Transport :: module(), TransOpts :: ranch:opts(), Protocol :: module(), ProtoOpts :: any()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start a listener.
A listener is a set of processes that accepts and manages connections using the given transport and protocol modules.
Arguments Ref The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the configuration.</description>
    </item>
    
    <item>
      <title>ranch:start_listener(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.start_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.start_listener/</guid>
      <description>Name ranch:start_listener - Start a listener
Description start_listener(Ref :: ranch_ref(), Transport :: module(), TransOpts :: ranch:opts(), Protocol :: module(), ProtoOpts :: any()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start a listener.
A listener is a set of processes that accepts and manages connections using the given transport and protocol modules.
Arguments Ref The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the configuration.</description>
    </item>
    
    <item>
      <title>ranch:start_listener(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.start_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.start_listener/</guid>
      <description>Name ranch:start_listener - Start a listener
Description start_listener(Ref :: ranch_ref(), Transport :: module(), TransOpts :: ranch:opts(), Protocol :: module(), ProtoOpts :: any()) -&amp;gt; {ok, ListenerPid :: pid()} | {error, any()}  Start a listener.
A listener is a set of processes that accepts and manages connections using the given transport and protocol modules.
Arguments Ref The listener name is used to refer to this listener in future calls, for example when stopping it or when updating the configuration.</description>
    </item>
    
    <item>
      <title>ranch:stop_listener(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.stop_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.stop_listener/</guid>
      <description>Name ranch:stop_listener - Stop a listener
Description stop_listener(Ref :: ranch_ref()) -&amp;gt; ok | {error, not_found}  Stop a listener.
The listener is stopped gracefully, first by closing the listening port, then by stopping the connection processes. These processes are stopped according to the shutdown transport option, which may be set to brutally kill all connection processes or give them some time to stop properly.
In order for the connection processes to exit gracefully, they need to trap exit signals and stop before the configured shutdown timeout.</description>
    </item>
    
    <item>
      <title>ranch:stop_listener(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.stop_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.stop_listener/</guid>
      <description>Name ranch:stop_listener - Stop a listener
Description stop_listener(Ref :: ranch_ref()) -&amp;gt; ok | {error, not_found}  Stop a listener.
The listener is stopped gracefully, first by closing the listening port, then by stopping the connection processes. These processes are stopped according to the shutdown transport option, which may be set to brutally kill all connection processes or give them some time to stop properly.
In order for the connection processes to exit gracefully, they need to trap exit signals and stop before the configured shutdown timeout.</description>
    </item>
    
    <item>
      <title>ranch:stop_listener(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.stop_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.stop_listener/</guid>
      <description>Name ranch:stop_listener - Stop a listener
Description stop_listener(Ref :: ranch_ref()) -&amp;gt; ok | {error, not_found}  Stop a listener.
The listener is stopped gracefully, first by closing the listening port, then by stopping the connection processes. These processes are stopped according to the shutdown transport option, which may be set to brutally kill all connection processes or give them some time to stop properly.
In order for the connection processes to exit gracefully, they need to trap exit signals and stop before the configured shutdown timeout.</description>
    </item>
    
    <item>
      <title>ranch:suspend_listener(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.suspend_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.suspend_listener/</guid>
      <description>Name ranch:suspend_listener - Suspend a running listener
Description suspend_listener(Ref :: ranch_ref()) -&amp;gt; ok | {error, any()}  Suspend a running listener.
Ranch will stop listening for and accepting connections and the listening socket will be closed. Existing connections will continue undisturbed. The function ranch:wait_for_connections(3) can be used to wait for connections to be closed if necessary.
Some transport options can only be changed when the listener is suspended. Please consult the ranch:set_transport_options(3) manual for more information.</description>
    </item>
    
    <item>
      <title>ranch:suspend_listener(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.suspend_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.suspend_listener/</guid>
      <description>Name ranch:suspend_listener - Suspend a running listener
Description suspend_listener(Ref :: ranch_ref()) -&amp;gt; ok | {error, any()}  Suspend a running listener.
Ranch will stop listening for and accepting connections and the listening socket will be closed. Existing connections will continue undisturbed. The function ranch:wait_for_connections(3) can be used to wait for connections to be closed if necessary.
Some transport options can only be changed when the listener is suspended. Please consult the ranch:set_transport_options(3) manual for more information.</description>
    </item>
    
    <item>
      <title>ranch:suspend_listener(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.suspend_listener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.suspend_listener/</guid>
      <description>Name ranch:suspend_listener - Suspend a running listener
Description suspend_listener(Ref :: ranch_ref()) -&amp;gt; ok | {error, any()}  Suspend a running listener.
Ranch will stop listening for and accepting connections and the listening socket will be closed. Existing connections will continue undisturbed. The function ranch:wait_for_connections(3) can be used to wait for connections to be closed if necessary.
Some transport options can only be changed when the listener is suspended. Please consult the ranch:set_transport_options(3) manual for more information.</description>
    </item>
    
    <item>
      <title>ranch:wait_for_connections(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.wait_for_connections/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch.wait_for_connections/</guid>
      <description>Name ranch:wait_for_connections - Wait for a specific number of connections
Description wait_for_connections(Ref :: ranch:ref(), Operator, NumConns :: non_neg_integer()) -&amp;gt; ok Operator :: &#39;&amp;gt;&#39; | &#39;&amp;gt;=&#39; | &#39;==&#39; | &#39;=&amp;lt;&#39; | &#39;&amp;lt;&#39;  Wait for a specific number of connections.
This function waits until the number of connections on the given listener becomes higher than, equal to or lower than the given number. It never returns otherwise.
This function can be used to gracefully shutdown a listener by first suspending the listener and then waiting for connections to terminate before finally stopping the listener.</description>
    </item>
    
    <item>
      <title>ranch:wait_for_connections(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.wait_for_connections/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch.wait_for_connections/</guid>
      <description>Name ranch:wait_for_connections - Wait for a specific number of connections
Description wait_for_connections(Ref :: ranch:ref(), Operator, NumConns :: non_neg_integer()) -&amp;gt; ok Operator :: &#39;&amp;gt;&#39; | &#39;&amp;gt;=&#39; | &#39;==&#39; | &#39;=&amp;lt;&#39; | &#39;&amp;lt;&#39;  Wait for a specific number of connections.
This function waits until the number of connections on the given listener becomes higher than, equal to or lower than the given number. It never returns otherwise.
This function can be used to gracefully shutdown a listener by first suspending the listener and then waiting for connections to terminate before finally stopping the listener.</description>
    </item>
    
    <item>
      <title>ranch:wait_for_connections(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.wait_for_connections/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch.wait_for_connections/</guid>
      <description>Name ranch:wait_for_connections - Wait for a specific number of connections
Description wait_for_connections(Ref :: ranch:ref(), Operator, NumConns :: non_neg_integer()) -&amp;gt; ok Operator :: &#39;&amp;gt;&#39; | &#39;&amp;gt;=&#39; | &#39;==&#39; | &#39;=&amp;lt;&#39; | &#39;&amp;lt;&#39;  Wait for a specific number of connections.
This function waits until the number of connections on the given listener becomes higher than, equal to or lower than the given number. It never returns otherwise.
This function can be used to gracefully shutdown a listener by first suspending the listener and then waiting for connections to terminate before finally stopping the listener.</description>
    </item>
    
    <item>
      <title>ranch_protocol(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/manual/ranch_protocol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/manual/ranch_protocol/</guid>
      <description>Name ranch_protocol - behaviour for protocol modules
Description The ranch_protocol behaviour defines the interface used by Ranch protocols.
Types None.
Callbacks start_link(Ref, Socket, Transport, ProtoOpts) -&amp;gt; {ok, pid()} | {ok, pid(), pid()} Ref = ranch:ref() Listener name.
 Socket = any() Socket for this connection.
 Transport = module() Transport module for this socket.
 ProtoOpts = any() Protocol options.
  Start a new connection process for the given socket.</description>
    </item>
    
    <item>
      <title>ranch_protocol(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/manual/ranch_protocol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/manual/ranch_protocol/</guid>
      <description>Name ranch_protocol - behaviour for protocol modules
Description The ranch_protocol behaviour defines the interface used by Ranch protocols.
Types None.
Callbacks start_link(Ref, Socket, Transport, ProtoOpts) -&amp;gt; {ok, pid()} | {ok, pid(), pid()} Ref = ranch:ref() Listener name.
 Socket = any() Socket for this connection.
 Transport = module() Transport module for this socket.
 ProtoOpts = any() Protocol options.
  Start a new connection process for the given socket.</description>
    </item>
    
    <item>
      <title>ranch_protocol(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch_protocol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch_protocol/</guid>
      <description>Name ranch_protocol - Protocol modules
Description The module ranch_protocol defines the interface used by Ranch protocols.
Callbacks Ranch protocols implement the following interface:
start_link(Ref :: ranch:ref(), _, Transport :: module(), ProtoOpts :: any()) -&amp;gt; {ok, ConnPid :: pid()} | {ok, SupPid :: pid(), ConnPid :: pid()}  Start a new connection process.
The only purpose of this callback is to start a process that will handle the socket. It must spawn the process, link and then return the new pid.</description>
    </item>
    
    <item>
      <title>ranch_protocol(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_protocol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_protocol/</guid>
      <description>Name ranch_protocol - Protocol modules
Description The module ranch_protocol defines the interface used by Ranch protocols.
Callbacks Ranch protocols implement the following interface:
start_link(Ref :: ranch:ref(), _, Transport :: module(), ProtoOpts :: any()) -&amp;gt; {ok, ConnPid :: pid()} | {ok, SupPid :: pid(), ConnPid :: pid()}  Start a new connection process.
The only purpose of this callback is to start a process that will handle the socket. It must spawn the process, link and then return the new pid.</description>
    </item>
    
    <item>
      <title>ranch_protocol(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_protocol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_protocol/</guid>
      <description>Name ranch_protocol - Protocol modules
Description The module ranch_protocol defines the interface used by Ranch protocols.
Callbacks Ranch protocols implement the following interface:
start_link(Ref :: ranch:ref(), Transport :: module(), ProtoOpts :: any()) -&amp;gt; {ok, ConnPid :: pid()} | {ok, SupPid :: pid(), ConnPid :: pid()}  Start a new connection process.
The only purpose of this callback is to start a process that will handle the socket. It must spawn the process, link and then return the new pid.</description>
    </item>
    
    <item>
      <title>ranch_proxy_header(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_proxy_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_proxy_header/</guid>
      <description>Name ranch_proxy_header - PROXY protocol
Description The module ranch_proxy_header provides functions for parsing and building the PROXY protocol header.
Exports ranch_proxy_header:parse(3) - Parse a PROXY protocol header  ranch_proxy_header:header(3) - Build a PROXY protocol header   Types proxy_info() proxy_info() = #{ %% Mandatory part. version := 1 | 2, command := local | proxy, transport_family =&amp;gt; undefined | ipv4 | ipv6 | unix, transport_protocol =&amp;gt; undefined | stream | dgram, %% Addresses.</description>
    </item>
    
    <item>
      <title>ranch_proxy_header(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_proxy_header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_proxy_header/</guid>
      <description>Name ranch_proxy_header - PROXY protocol
Description The module ranch_proxy_header provides functions for parsing and building the PROXY protocol header.
Exports ranch_proxy_header:parse(3) - Parse a PROXY protocol header  ranch_proxy_header:header(3) - Build a PROXY protocol header   Types proxy_info() proxy_info() = #{ %% Mandatory part. version := 1 | 2, command := local | proxy, transport_family =&amp;gt; undefined | ipv4 | ipv6 | unix, transport_protocol =&amp;gt; undefined | stream | dgram, %% Addresses.</description>
    </item>
    
    <item>
      <title>ranch_proxy_header:header(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_proxy_header.header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_proxy_header.header/</guid>
      <description>Name ranch_proxy_header:header - Build a PROXY protocol header
Description header(ProxyInfo) -&amp;gt; header(ProxyInfo, #{}) header(ProxyInfo, BuildOpts) -&amp;gt; iodata() ProxyInfo :: ranch_proxy_header:proxy_info() BuildOpts :: #{ checksum =&amp;gt; crc32c, padding =&amp;gt; pos_integer() %% &amp;gt;= 3 }  Build a PROXY protocol header.
Arguments ProxyInfo The proxy information to encode.
 BuildOpts Options to control whether to add a checksum or padding should be included in the encoded PROXY protocol header.
  Return value The PROXY protocol header is returned.</description>
    </item>
    
    <item>
      <title>ranch_proxy_header:header(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_proxy_header.header/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_proxy_header.header/</guid>
      <description>Name ranch_proxy_header:header - Build a PROXY protocol header
Description header(ProxyInfo) -&amp;gt; header(ProxyInfo, #{}) header(ProxyInfo, BuildOpts) -&amp;gt; iodata() ProxyInfo :: ranch_proxy_header:proxy_info() BuildOpts :: #{ checksum =&amp;gt; crc32c, padding =&amp;gt; pos_integer() %% &amp;gt;= 3 }  Build a PROXY protocol header.
Arguments ProxyInfo The proxy information to encode.
 BuildOpts Options to control whether to add a checksum or padding should be included in the encoded PROXY protocol header.
  Return value The PROXY protocol header is returned.</description>
    </item>
    
    <item>
      <title>ranch_proxy_header:parse(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_proxy_header.parse/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_proxy_header.parse/</guid>
      <description>Name ranch_proxy_header:parse - Parse a PROXY protocol header
Description parse(Data :: binary()) -&amp;gt; {ok, ranch_proxy_header:proxy_info(), Rest :: binary()} | {error, HumanReadable :: atom()}  Parse a PROXY protocol header.
Arguments Data The PROXY protocol header optionally followed by more data.
  Return value An ok tuple is returned on success, containing the proxy information found in the header and the rest of the data if more was provided.
An error tuple is returned when a protocol error is detected.</description>
    </item>
    
    <item>
      <title>ranch_proxy_header:parse(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_proxy_header.parse/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_proxy_header.parse/</guid>
      <description>Name ranch_proxy_header:parse - Parse a PROXY protocol header
Description parse(Data :: binary()) -&amp;gt; {ok, ranch_proxy_header:proxy_info(), Rest :: binary()} | {error, HumanReadable :: atom()}  Parse a PROXY protocol header.
Arguments Data The PROXY protocol header optionally followed by more data.
  Return value An ok tuple is returned on success, containing the proxy information found in the header and the rest of the data if more was provided.
An error tuple is returned when a protocol error is detected.</description>
    </item>
    
    <item>
      <title>ranch_ssl(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/manual/ranch_ssl/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/manual/ranch_ssl/</guid>
      <description>Name ranch_ssl - SSL transport module
Description The ranch_ssl module implements an SSL Ranch transport.
Types ssl_opt() ssl_opt() = {alpn_preferred_protocols, [binary()]} | {beast_mitigation, one_n_minus_one | zero_n | disabled} | {cacertfile, string()} | {cacerts, [public_key:der_encoded()]} | {cert, public_key:der_encoded()} | {certfile, string()} | {ciphers, [ssl:erl_cipher_suite()] | string()} | {client_renegotiation, boolean()} | {crl_cache, {module(), {internal | any(), list()}}} | {crl_check, boolean() | peer | best_effort} | {depth, 0..255} | {dh, public_key:der_encoded()} | {dhfile, string()} | {fail_if_no_peer_cert, boolean()} | {hibernate_after, integer() | undefined} | {honor_cipher_order, boolean()} | {key, {&#39;RSAPrivateKey&#39; | &#39;DSAPrivateKey&#39; | &#39;PrivateKeyInfo&#39;, public_key:der_encoded()}} | {keyfile, string()} | {log_alert, boolean()} | {next_protocols_advertised, [binary()]} | {padding_check, boolean()} | {partial_chain, fun(([public_key:der_encoded()]) -&amp;gt; {trusted_ca, public_key:der_encoded()} | unknown_ca)} | {password, string()} | {psk_identity, string()} | {reuse_session, fun()} | {reuse_sessions, boolean()} | {secure_renegotiate, boolean()} | {signature_algs, [{atom(), atom()}]} | {sni_fun, fun()} | {sni_hosts, [{string(), ssl_opt()}]} | {user_lookup_fun, {fun(), any()}} | {v2_hello_compatible, boolean()} | {verify, ssl:verify_type()} | {verify_fun, {fun(), any()}} | {versions, [atom()]}.</description>
    </item>
    
    <item>
      <title>ranch_ssl(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/manual/ranch_ssl/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/manual/ranch_ssl/</guid>
      <description>Name ranch_ssl - SSL transport module
Description The ranch_ssl module implements an SSL Ranch transport.
Types ssl_opt() ssl_opt() = {alpn_preferred_protocols, [binary()]} | {beast_mitigation, one_n_minus_one | zero_n | disabled} | {cacertfile, string()} | {cacerts, [public_key:der_encoded()]} | {cert, public_key:der_encoded()} | {certfile, string()} | {ciphers, [ssl:erl_cipher_suite()] | string()} | {client_renegotiation, boolean()} | {crl_cache, {module(), {internal | any(), list()}}} | {crl_check, boolean() | peer | best_effort} | {depth, 0..255} | {dh, public_key:der_encoded()} | {dhfile, string()} | {fail_if_no_peer_cert, boolean()} | {hibernate_after, integer() | undefined} | {honor_cipher_order, boolean()} | {key, {&#39;RSAPrivateKey&#39; | &#39;DSAPrivateKey&#39; | &#39;PrivateKeyInfo&#39;, public_key:der_encoded()}} | {keyfile, string()} | {log_alert, boolean()} | {next_protocols_advertised, [binary()]} | {padding_check, boolean()} | {partial_chain, fun(([public_key:der_encoded()]) -&amp;gt; {trusted_ca, public_key:der_encoded()} | unknown_ca)} | {password, string()} | {psk_identity, string()} | {reuse_session, fun()} | {reuse_sessions, boolean()} | {secure_renegotiate, boolean()} | {signature_algs, [{atom(), atom()}]} | {sni_fun, fun()} | {sni_hosts, [{string(), ssl_opt()}]} | {user_lookup_fun, {fun(), any()}} | {v2_hello_compatible, boolean()} | {verify, ssl:verify_type()} | {verify_fun, {fun(), any()}} | {versions, [atom()]}.</description>
    </item>
    
    <item>
      <title>ranch_ssl(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch_ssl/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch_ssl/</guid>
      <description>Name ranch_ssl - SSL transport
Description The module ranch_ssl implements an SSL Ranch transport.
Exports The module ranch_ssl implements the interface defined by ranch_transport(3).
Types opt() opt() :: ranch_tcp:opt() | ssl_opt()  Listen options.
The TCP options are defined in ranch_tcp(3).
opts() opts() :: [opt()]  List of listen options.
ssl_opt() ssl_opt() = {alpn_preferred_protocols, [binary()]} | {beast_mitigation, one_n_minus_one | zero_n | disabled} | {cacertfile, string()} | {cacerts, [public_key:der_encoded()]} | {cert, public_key:der_encoded()} | {certfile, string()} | {ciphers, [ssl:erl_cipher_suite()] | string()} | {client_renegotiation, boolean()} | {crl_cache, {module(), {internal | any(), list()}}} | {crl_check, boolean() | peer | best_effort} | {depth, 0.</description>
    </item>
    
    <item>
      <title>ranch_ssl(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_ssl/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_ssl/</guid>
      <description>Name ranch_ssl - SSL transport
Description The module ranch_ssl implements an SSL Ranch transport.
Exports The module ranch_ssl implements the interface defined by ranch_transport(3).
Types opt() opt() :: ranch_tcp:opt() | ssl_opt()  Listen options.
The TCP options are defined in ranch_tcp(3).
opts() opts() :: [opt()]  List of listen options.
ssl_opt() ssl_opt() = {alpn_preferred_protocols, [binary()]} | {beast_mitigation, one_n_minus_one | zero_n | disabled} | {cacertfile, string()} | {cacerts, [public_key:der_encoded()]} | {cert, public_key:der_encoded()} | {certfile, string()} | {ciphers, [ssl:erl_cipher_suite()] | string()} | {client_renegotiation, boolean()} | {crl_cache, {module(), {internal | any(), list()}}} | {crl_check, boolean() | peer | best_effort} | {depth, 0.</description>
    </item>
    
    <item>
      <title>ranch_ssl(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_ssl/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_ssl/</guid>
      <description>Name ranch_ssl - SSL transport
Description The module ranch_ssl implements an SSL Ranch transport.
Exports The module ranch_ssl implements the interface defined by ranch_transport(3).
Types opt() opt() :: ranch_tcp:opt() | ssl_opt()  Listen options.
The TCP options are defined in ranch_tcp(3).
opts() opts() :: [opt()]  List of listen options.
ssl_opt() ssl_opt() = {alpn_preferred_protocols, [binary()]} | {beast_mitigation, one_n_minus_one | zero_n | disabled} | {cacertfile, file:filename()} | {cacerts, [public_key:der_encoded()]} | {cert, public_key:der_encoded()} | {certfile, file:filename()} | {ciphers, ssl:ciphers()} | {client_renegotiation, boolean()} | {crl_cache, [any()]} | {crl_check, boolean() | peer | best_effort} | {depth, integer()} | {dh, binary()} | {dhfile, file:filename()} | {eccs, [atom()]} | {fail_if_no_peer_cert, boolean()} | {handshake, hello | full} | {hibernate_after, timeout()} | {honor_cipher_order, boolean()} | {honor_ecc_order, boolean()} | {key, ssl:key()} | {keyfile, file:filename()} | {log_alert, boolean()} | {log_level, logger:level()} | {max_handshake_size, integer()} | {next_protocols_advertised, [binary()]} | {padding_check, boolean()} | {partial_chain, fun()} | {password, string()} | {protocol, tls | dtls} | {psk_identity, string()} | {reuse_session, fun()} | {reuse_sessions, boolean()} | {secure_renegotiate, boolean()} | {signature_algs, [{ssl:hash(), ssl:sign_algo()}]} | {signature_algs_cert, [atom()]} | {sni_fun, fun()} | {sni_hosts, [{string(), ssl_opt()}]} | {user_lookup_fun, {fun(), any()}} | {verify, verify_none | verify_peer} | {verify_fun, {fun(), any()}} | {versions, [ssl:protocol_version()]}  SSL-specific listen options.</description>
    </item>
    
    <item>
      <title>ranch_tcp(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/manual/ranch_tcp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/manual/ranch_tcp/</guid>
      <description>Name ranch_tcp - TCP transport module
Description The ranch_tcp module implements a TCP Ranch transport.
Note that due to bugs in OTP up to at least R16B02, it is recommended to disable async threads when using the sendfile function of this transport, as it can make the threads stuck indefinitely.
Types opt() opt() = {backlog, non_neg_integer()} | {buffer, non_neg_integer()} | {delay_send, boolean()} | {dontroute, boolean()} | {exit_on_close, boolean()} | {fd, non_neg_integer()} | {high_msgq_watermark, non_neg_integer()} | {high_watermark, non_neg_integer()} | inet | inet6 | {ip, inet:ip_address()} | {ipv6_v6only, boolean()} | {keepalive, boolean()} | {linger, {boolean(), non_neg_integer()}} | {low_msgq_watermark, non_neg_integer()} | {low_watermark, non_neg_integer()} | {nodelay, boolean()} | {port, inet:port_number()} | {priority, integer()} | {raw, non_neg_integer(), non_neg_integer(), binary()} | {recbuf, non_neg_integer()} | {send_timeout, timeout()} | {send_timeout_close, boolean()} | {sndbuf, non_neg_integer()} | {tos, integer()}  Listen options.</description>
    </item>
    
    <item>
      <title>ranch_tcp(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/manual/ranch_tcp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/manual/ranch_tcp/</guid>
      <description>Name ranch_tcp - TCP transport module
Description The ranch_tcp module implements a TCP Ranch transport.
Note that due to bugs in OTP up to at least R16B02, it is recommended to disable async threads when using the sendfile function of this transport, as it can make the threads stuck indefinitely.
Types opt() opt() = {backlog, non_neg_integer()} | {buffer, non_neg_integer()} | {delay_send, boolean()} | {dontroute, boolean()} | {exit_on_close, boolean()} | {fd, non_neg_integer()} | {high_msgq_watermark, non_neg_integer()} | {high_watermark, non_neg_integer()} | inet | inet6 | {ip, inet:ip_address()} | {ipv6_v6only, boolean()} | {keepalive, boolean()} | {linger, {boolean(), non_neg_integer()}} | {low_msgq_watermark, non_neg_integer()} | {low_watermark, non_neg_integer()} | {nodelay, boolean()} | {port, inet:port_number()} | {priority, integer()} | {raw, non_neg_integer(), non_neg_integer(), binary()} | {recbuf, non_neg_integer()} | {send_timeout, timeout()} | {send_timeout_close, boolean()} | {sndbuf, non_neg_integer()} | {tos, integer()}  Listen options.</description>
    </item>
    
    <item>
      <title>ranch_tcp(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch_tcp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch_tcp/</guid>
      <description>Name ranch_tcp - TCP transport
Description The module ranch_tcp implements a TCP Ranch transport.
The function sendfile may not work correctly when used against files stored in a VirtualBox shared folder.
Exports The module ranch_tcp implements the interface defined by ranch_transport(3).
Types opt() opt() = {backlog, non_neg_integer()} | {buffer, non_neg_integer()} | {delay_send, boolean()} | {dontroute, boolean()} | {exit_on_close, boolean()} | {fd, non_neg_integer()} | {high_msgq_watermark, non_neg_integer()} | {high_watermark, non_neg_integer()} | inet | inet6 | {ip, inet:ip_address()} | {ipv6_v6only, boolean()} | {keepalive, boolean()} | {linger, {boolean(), non_neg_integer()}} | {low_msgq_watermark, non_neg_integer()} | {low_watermark, non_neg_integer()} | {nodelay, boolean()} | {port, inet:port_number()} | {priority, integer()} | {raw, non_neg_integer(), non_neg_integer(), binary()} | {recbuf, non_neg_integer()} | {send_timeout, timeout()} | {send_timeout_close, boolean()} | {sndbuf, non_neg_integer()} | {tos, integer()}  Listen options.</description>
    </item>
    
    <item>
      <title>ranch_tcp(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_tcp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_tcp/</guid>
      <description>Name ranch_tcp - TCP transport
Description The module ranch_tcp implements a TCP Ranch transport.
The function sendfile may not work correctly when used against files stored in a VirtualBox shared folder.
Exports The module ranch_tcp implements the interface defined by ranch_transport(3).
Types opt() opt() = {backlog, non_neg_integer()} | {buffer, non_neg_integer()} | {delay_send, boolean()} | {dontroute, boolean()} | {exit_on_close, boolean()} | {fd, non_neg_integer()} | {high_msgq_watermark, non_neg_integer()} | {high_watermark, non_neg_integer()} | inet | inet6 | {ip, inet:ip_address()} | {ipv6_v6only, boolean()} | {keepalive, boolean()} | {linger, {boolean(), non_neg_integer()}} | {low_msgq_watermark, non_neg_integer()} | {low_watermark, non_neg_integer()} | {nodelay, boolean()} | {port, inet:port_number()} | {priority, integer()} | {raw, non_neg_integer(), non_neg_integer(), binary()} | {recbuf, non_neg_integer()} | {send_timeout, timeout()} | {send_timeout_close, boolean()} | {sndbuf, non_neg_integer()} | {tos, integer()}  Listen options.</description>
    </item>
    
    <item>
      <title>ranch_tcp(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_tcp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_tcp/</guid>
      <description>Name ranch_tcp - TCP transport
Description The module ranch_tcp implements a TCP Ranch transport.
The function sendfile may not work correctly when used against files stored in a VirtualBox shared folder.
Exports The module ranch_tcp implements the interface defined by ranch_transport(3).
Types opt() opt() = {backlog, non_neg_integer()} | {buffer, non_neg_integer()} | {delay_send, boolean()} | {dontroute, boolean()} | {exit_on_close, boolean()} | {fd, non_neg_integer()} | {high_msgq_watermark, non_neg_integer()} | {high_watermark, non_neg_integer()} | inet | inet6 | {ip, inet:ip_address() | inet:local_address()} | {ipv6_v6only, boolean()} | {keepalive, boolean()} | {linger, {boolean(), non_neg_integer()}} | {low_msgq_watermark, non_neg_integer()} | {low_watermark, non_neg_integer()} | {nodelay, boolean()} | {port, inet:port_number()} | {priority, integer()} | {raw, non_neg_integer(), non_neg_integer(), binary()} | {recbuf, non_neg_integer()} | {send_timeout, timeout()} | {send_timeout_close, boolean()} | {sndbuf, non_neg_integer()} | {tos, integer()}  Listen options.</description>
    </item>
    
    <item>
      <title>ranch_transport(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.4/manual/ranch_transport/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.4/manual/ranch_transport/</guid>
      <description>Name ranch_transport - behaviour for transport modules
Description The ranch_transport behaviour defines the interface used by Ranch transports.
Types sendfile_opts() = [{chunk_size, non_neg_integer()}] Options used by the sendfile function and callbacks.
Allows configuring the chunk size, in bytes. Defaults to 8191 bytes.
Callbacks accept(LSocket, Timeout) -&amp;gt; {ok, CSocket} | {error, closed | timeout | atom()} LSocket = CSocket = any() Listening socket.
 Timeout = timeout() Accept timeout.
  Accept a connection on the given listening socket.</description>
    </item>
    
    <item>
      <title>ranch_transport(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.5/manual/ranch_transport/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.5/manual/ranch_transport/</guid>
      <description>Name ranch_transport - behaviour for transport modules
Description The ranch_transport behaviour defines the interface used by Ranch transports.
Types sendfile_opts() = [{chunk_size, non_neg_integer()}] Options used by the sendfile function and callbacks.
Allows configuring the chunk size, in bytes. Defaults to 8191 bytes.
Callbacks accept(LSocket, Timeout) -&amp;gt; {ok, CSocket} | {error, closed | timeout | atom()} LSocket = CSocket = any() Listening socket.
 Timeout = timeout() Accept timeout.
  Accept a connection on the given listening socket.</description>
    </item>
    
    <item>
      <title>ranch_transport(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch_transport/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch_transport/</guid>
      <description>Name ranch_transport - Transport modules
Description The module ranch_transport defines the interface used by Ranch transports.
Callbacks Ranch transports implement the following interface:
accept accept(LSocket :: socket(), Timeout :: timeout()) -&amp;gt; {ok, Socket :: socket()} | {error, closed | timeout | atom()}  Use the listening socket returned by listen/1 to accept a new connection. The timeout is specified in milliseconds.
close close(Socket :: socket()) -&amp;gt; ok  Close the socket.</description>
    </item>
    
    <item>
      <title>ranch_transport(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_transport/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_transport/</guid>
      <description>Name ranch_transport - Transport modules
Description The module ranch_transport defines the interface used by Ranch transports.
Callbacks Ranch transports implement the following interface:
accept accept(LSocket :: socket(), Timeout :: timeout()) -&amp;gt; {ok, Socket :: socket()} | {error, closed | timeout | atom()}  Use the listening socket returned by listen/1 to accept a new connection. The timeout is specified in milliseconds.
close close(Socket :: socket()) -&amp;gt; ok  Close the socket.</description>
    </item>
    
    <item>
      <title>ranch_transport(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_transport/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_transport/</guid>
      <description>Name ranch_transport - Transport modules
Description The module ranch_transport defines the interface used by Ranch transports.
Callbacks Ranch transports implement the following interface:
accept accept(LSocket :: socket(), Timeout :: timeout()) -&amp;gt; {ok, Socket :: socket()} | {error, closed | timeout | atom()}  Use the listening socket returned by listen/1 to accept a new connection. The timeout is specified in milliseconds.
close close(Socket :: socket()) -&amp;gt; ok  Close the socket.</description>
    </item>
    
    <item>
      <title>ranch_transport:sendfile(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch_transport.sendfile/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.6/manual/ranch_transport.sendfile/</guid>
      <description>Name ranch_transport:sendfile - Send a file on the socket
Description sendfile(Transport :: module(), Socket :: ranch_transport:socket(), File :: file:name_all() | file:fd(), Offset :: non_neg_integer(), Bytes :: non_neg_integer(), Opts :: ranch_transport:sendfile_opts()) -&amp;gt; {ok, SentBytes :: non_neg_integer()} | {error, atom()}  Send a file on the socket.
The file may be sent full or in parts, and may be specified by its filename or by an already open file descriptor.
This function emulates the function file:sendfile/2,4,5 and may be used when transports are not manipulating TCP directly.</description>
    </item>
    
    <item>
      <title>ranch_transport:sendfile(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_transport.sendfile/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/1.7/manual/ranch_transport.sendfile/</guid>
      <description>Name ranch_transport:sendfile - Send a file on the socket
Description sendfile(Transport :: module(), Socket :: ranch_transport:socket(), File :: file:name_all() | file:fd(), Offset :: non_neg_integer(), Bytes :: non_neg_integer(), Opts :: ranch_transport:sendfile_opts()) -&amp;gt; {ok, SentBytes :: non_neg_integer()} | {error, atom()}  Send a file on the socket.
The file may be sent full or in parts, and may be specified by its filename or by an already open file descriptor.
This function emulates the function file:sendfile/2,4,5 and may be used when transports are not manipulating TCP directly.</description>
    </item>
    
    <item>
      <title>ranch_transport:sendfile(3)</title>
      <link>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_transport.sendfile/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://ninenines.eu/docs/en/ranch/2.0/manual/ranch_transport.sendfile/</guid>
      <description>Name ranch_transport:sendfile - Send a file on the socket
Description sendfile(Transport :: module(), Socket :: ranch_transport:socket(), File :: file:name_all() | file:fd(), Offset :: non_neg_integer(), Bytes :: non_neg_integer(), Opts :: ranch_transport:sendfile_opts()) -&amp;gt; {ok, SentBytes :: non_neg_integer()} | {error, atom()}  Send a file on the socket.
The file may be sent full or in parts, and may be specified by its filename or by an already open file descriptor.
This function emulates the function file:sendfile/2,4,5 and may be used when transports are not manipulating TCP directly.</description>
    </item>
    
  </channel>
</rss>