-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Expand file tree
/
Copy pathhttpd.erl
More file actions
1587 lines (1314 loc) · 60.3 KB
/
Copy pathhttpd.erl
File metadata and controls
1587 lines (1314 loc) · 60.3 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
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
%%
%% %CopyrightBegin%
%%
%% SPDX-License-Identifier: Apache-2.0
%%
%% Copyright Ericsson AB 1997-2026. All Rights Reserved.
%%
%% Licensed under the Apache License, Version 2.0 (the "License");
%% you may not use this file except in compliance with the License.
%% You may obtain a copy of the License at
%%
%% http://www.apache.org/licenses/LICENSE-2.0
%%
%% Unless required by applicable law or agreed to in writing, software
%% distributed under the License is distributed on an "AS IS" BASIS,
%% WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
%% See the License for the specific language governing permissions and
%% limitations under the License.
%%
%% %CopyrightEnd%
%%
%%
-module(httpd).
-moduledoc """
HTTP server API
An implementation of an HTTP 1.1 compliant web server, as defined in
[RFC 2616](http://www.ietf.org/rfc/rfc2616.txt). Provides web server start
options, administrative functions, and an Erlang callback API.
## Data types
Type definitions that are used more than once in this module:
`boolean() = true | false`
`t:string/0` = list of ASCII characters
`path() = string()` representing a file or a directory path
`ip_address() = {N1,N2,N3,N4} % IPv4 | {K1,K2,K3,K4,K5,K6,K7,K8} % IPv6`
`hostname() = string()` representing a host, for example, "foo.bar.com"
`property() = atom()`
## HTTP server service start & stop
A web server can be configured to start when starting the `Inets` application,
or dynamically in runtime by calling the `Inets` application API
`inets:start(httpd, ServiceConfig)` or `inets:start(httpd, ServiceConfig, How)`,
see `m:inets`. The configuration options, also called properties, are as
follows:
[](){: #props_file }
### File Properties
When the web server is started at application start time, the properties are to
be fetched from a configuration file that can consist of a regular Erlang
property list, that is, `[{Option, Value}]`, where `Option = property() `and
`Value = term()`, followed by a full stop. If the web server is started
dynamically at runtime, a file can still be specified but also the complete
property list.
- [](){: #prop_proplist_file } **`{proplist_file, path()}`**
If this property is defined, `Inets` expects to find all other properties
defined in this file. The file must include all properties listed under
mandatory properties.
> #### Note {: .info }
>
> Note support for legacy configuration file with Apache syntax is dropped in
> OTP-23.
[](){: #props_mand }
### Mandatory Properties
- [](){: #prop_port } **`{port, integer()}`**
The port that the HTTP server listen to. If zero is specified as port, an
arbitrary available port is picked and function `httpd:info/2` can be used to
determine which port was picked.
- [](){: #prop_server_root } **`{server_root, path()}`**
Defines the home directory of the server, where log files, and so on, can be
stored. Relative paths specified in other properties refer to this directory.
- [](){: #prop_doc_root } **`{document_root, path()}`**
Defines the top directory for the documents that are available on the HTTP
server.
[](){: #props_comm }
### Communication Properties
- [](){: #prop_bind_address } **`{bind_address, ip_address() | hostname() |
any}`**
Default is `any`
- [](){: #prop_server_name } **`{server_name, string()}`**
The name of your server, normally a fully qualified domain name.
If not given, this defaults to `net_adm:localhost()`.
- [](){: #profile } **`{profile, atom()}`**
Used together with [`bind_address`](`m:httpd#prop_bind_address`) and
[`port`](`m:httpd#prop_port`) to uniquely identify a HTTP server. This can be
useful in a virtualized environment, where there can be more that one server
that has the same bind_address and port. If this property is not explicitly
set, it is assumed that the [`bind_address`](`m:httpd#prop_bind_address`) and
[`port`](`m:httpd#prop_port`) uniquely identifies the HTTP server.
- [](){: #prop_socket_type } **`{socket_type, ip_comm | {ip_comm, Config::proplist()} | {ssl, Config::proplist()}}`**
For `ip_comm` configuration options, see `gen_tcp:listen/2`, some options that
are used internally by httpd cannot be set.
For `SSL` configuration options, see `ssl:listen/2`.
Default is `ip_comm`.
> #### Note {: .info }
>
> OTP-25 deprecates the communication properties
> `{socket_type, ip_comm | {ip_comm, Config::proplist()} | {essl, Config::proplist()}}`
> replacing it by
> `{socket_type, ip_comm | {ip_comm, Config::proplist()} | {ssl, Config::proplist()}}`.
- [](){: #prop_ipfamily } **`{ipfamily, inet | inet6}`**
Default is `inet`, legacy option `inet6fb4` no longer makes sense and will be
translated to inet.
- [](){: #prop_minimum_bytes_per_second } **`{minimum_bytes_per_second,
integer()}`**
If given, sets a minimum of bytes per second value for connections.
If the value is unreached, the socket closes for that connection.
The option is good for reducing the risk of "slow DoS" attacks.
[](){: #props_api_modules }
### Erlang Web Server API Modules
- [](){: #prop_modules } **`{modules, [atom()]}`**
Defines which modules the HTTP server uses when handling requests. Default is
`[mod_alias, mod_auth, mod_esi, mod_dir, mod_get, mod_head, mod_log, mod_disk_log]`.
Notice that some `mod`\-modules are dependent on others, so the order cannot
be entirely arbitrary. See the [Inets Web Server Modules](http_server.md) in
the User's Guide for details.
[](){: #props_limit }
### Limit properties
- [](){: #prop_customize } **`{customize, atom()}`**
A callback module to customize the inets HTTP servers behaviour see
`m:httpd_custom_api`
- [](){: #prop_disable_chunked_encoding }
**`{disable_chunked_transfer_encoding_send, boolean()}`**
Allows you to disable chunked transfer-encoding when sending a response to an
HTTP/1.1 client. Default is `false`.
- [](){: #prop_keep_alive } **`{keep_alive, boolean()}`**
Instructs the server whether to use persistent connections when the client
claims to be HTTP/1.1 compliant. Default is `true`.
- [](){: #prop_keep_alive_timeout } **`{keep_alive_timeout, integer()}`**
The number of seconds the server waits for a subsequent request from the
client before closing the connection. Default is `150`.
- [](){: #prop_max_body_size } **`{max_body_size, integer()}`**
Limits the size of the message body of an HTTP request. Default is no limit.
- [](){: #prop_max_clients } **`{max_clients, integer()}`**
Limits the number of simultaneous requests that can be supported. Default is
`150`.
- [](){: #prop_max_header_size } **`{max_header_size, integer()}`**
Limits the size of the message header of an HTTP request. Default is `10240`.
- [](){: #prop_max_content_length } **`{max_content_length, integer()}`**
Maximum content-length in an incoming request, in bytes. Requests with content
larger than this are answered with status 413. Default is `100000000` (100
MB).
- [](){: #prop_max_uri } **`{max_uri_size, integer()}`**
Limits the size of the HTTP request URI. Default is no limit.
- [](){: #prop_max_keep_alive_req } **`{max_keep_alive_request, integer()}`**
The number of requests that a client can do on one connection. When the server
has responded to the number of requests defined by `max_keep_alive_requests`,
the server closes the connection. The server closes it even if there are
queued request. Default is no limit.
[](){: #props_admin }
### Administrative Properties
- [](){: #prop_mime_types } **`{mime_types, [{MimeType, Extension}] | path()}`**
`MimeType = string()` and `Extension = string()`. Files delivered to the
client are MIME typed according to RFC 1590. File suffixes are mapped to MIME
types before file delivery. The mapping between file suffixes and MIME types
can be specified in the property list.
Mime types can also be read from a file. The file should contain lines in the
form `MediaType [Extensions...]`, such as `text/html html htm`. To configure
this, specify the path to it, such as `{mime_types, "/etc/mime.types"}`.
If unset, `conf/mime.types` under `server_root` will be used if it exists,
otherwise, the default is `[{"html","text/html"},{"htm","text/html"}]`.
- [](){: #prop_mime_type } **`{mime_type, string()}`**
When the server is asked to provide a document type that cannot be determined
by the MIME Type Settings, the server uses this default type.
- [](){: #prop_server_admin } **`{server_admin, string()}`**
Defines the email-address of the server administrator to be included in any
error messages returned by the server.
- [](){: #prop_server_tokens } **`{server_tokens,
none|prod|major|minor|minimal|os|full|{private, string()}}`**
Defines the look of the value of the server header.
Example: Assuming the version of `Inets` is 5.8.1, the server header string
can look as follows for the different values of server-tokens:
- **`none`** - "" % A Server: header will not be generated
- **`prod`** - "inets"
- **`major`** - "inets/5"
- **`minor`** - "inets/5.8"
- **`minimal`** - "inets/5.8.1"
- **`os`** - "inets/5.8.1 (unix)"
- **`full`** - "inets/5.8.1 (unix/linux) OTP/R15B"
- **`{private, "foo/bar"}`** - "foo/bar"
By default, the value is as before, that is, `minimal`.
- [](){: #prop_logger } **`{logger, Options::list()}`**
Currently only one option is supported:
- **`{error, ServerID::atom()}`** - Produces
[logger events](`t:logger:log_event/0`) on logger
[level error](`t:logger:level/0`) under the hierarchical logger
[domain:](`t:logger:log_event/0`) `[otp, inets, httpd, ServerID, error]` The
built in logger formatting function produces log entries from the error
reports:
```c
#{server_name => string()
protocol => internal | 'TCP' | 'TLS' | 'HTTP',
transport => "TCP" | "TLS", %% Present when protocol = 'HTTP'
uri => string(), %% Present when protocol = 'HTTP' and URI is valid
peer => inet:peername(),
host => inet:hostname(),
reason => term()
}
```
An example of a log entry with only default settings of logger
```text
=ERROR REPORT==== 9-Oct-2019::09:33:27.350235 ===
Server: My Server
Protocol: HTTP
Transport: TLS
URI: /not_there
Host: 127.0.1.1:80
Peer: 127.0.0.1:45253
Reason: [{statuscode,404},{description,"Object Not Found"}]
```
Using this option makes mod_log and mod_disk_log error logs redundant.
Add the filter
```erlang
{fun logger_filters:domain/2,
{log,equal,[otp,inets, httpd, ServerID, error]}
```
to appropriate logger handler to handle the events. For example to write the
error log from an httpd server with a `ServerID` of `my_server` to a file
you can use the following sys.config:
```erlang
[{kernel,
[{logger,
[{handler, http_error_test, logger_std_h,
#{config => #{ file => "log/http_error.log" },
filters => [{inets_httpd, {fun logger_filters:domain/2,
{log, equal,
[otp, inets, httpd, my_server, error]
}}}],
filter_default => stop }}]}]}].
```
or if you want to add it to the default logger via an API:
```erlang
logger:add_handler_filter(default,
inets_httpd,
{fun logger_filters:domain/2,
{log, equal,
[otp, inets, httpd, my_server, error]}}).
```
- [](){: #prop_log_format } **`{log_format, common | combined}`**
Defines if access logs are to be written according to the `common` log format
or the extended common log format. The `common` format is one line looking
like this: `remotehost rfc931 authuser [date] "request" status bytes`.
Here:
- **`remotehost`** - Remote.
- **`rfc931`** - The remote username of the client
([RFC 931](http://www.ietf.org/rfc/rfc931.txt)).
- **`authuser`** - The username used for authentication.
- **`[date]`** - Date and time of the request
([RFC 1123](http://www.ietf.org/rfc/rfc1123.txt)).
- **`"request"`** - The request line as it came from the client
([RFC 1945](http://www.ietf.org/rfc/rfc1945.txt)).
- **`status`** - The HTTP status code returned to the client
([RFC 1945](http://www.ietf.org/rfc/rfc1945.txt)).
- **`bytes`** - The content-length of the document transferred.
The `combined` format is one line looking like this:
`remotehost rfc931 authuser [date] "request" status bytes "referer" "user_agent"`
In addition to the earlier:
- **`"referer"`** - The URL the client was on before requesting the URL (if it
could not be determined, a minus sign is placed in this field).
- **`"user_agent"`** - The software the client claims to be using (if it could
not be determined, a minus sign is placed in this field).
This affects the access logs written by `mod_log` and `mod_disk_log`.
- [](){: #prop_elog_format } **`{error_log_format, pretty | compact}`**
Default is `pretty`. If the error log is meant to be read directly by a human,
`pretty` is the best option.
`pretty` has a format corresponding to:
```erlang
io:format("[~s] ~s, reason: ~n ~p ~n~n", [Date, Msg, Reason]).
```
`compact` has a format corresponding to:
```erlang
io:format("[~s] ~s, reason: ~w ~n", [Date, Msg, Reason]).
```
This affects the error logs written by `mod_log` and `mod_disk_log`.
[](){: #props_alias }
### URL Aliasing Properties - Requires mod_alias
- [](){: #prop_alias } **`{alias, {Alias, RealName}}`**
`Alias = string()` and `RealName = string()`. `alias` allows documents to be
stored in the local file system instead of the `document_root` location. URLs
with a path beginning with url-path is mapped to local files beginning with
directory-filename, for example:
```erlang
{alias, {"/image", "/ftp/pub/image"}}
```
Access to http://your.server.org/image/foo.gif would refer to the file
/ftp/pub/image/foo.gif.
- [](){: #prop_re_write } **`{re_write, {Re, Replacement}}`**
`Re = string()` and `Replacement = string()`. `re_write` allows documents to
be stored in the local file system instead of the `document_root` location.
URLs are rewritten by `re:replace/3` to produce a path in the local
file-system, for example:
```erlang
{re_write, {"^/[~]([^/]+)(.*)$", "/home/\\1/public\\2"}}
```
Access to http://your.server.org/~bob/foo.gif would refer to the file
/home/bob/public/foo.gif.
- [](){: #prop_dir_idx } **`{directory_index, [string()]}`**
`directory_index` specifies a list of resources to look for if a client
requests a directory using a `/` at the end of the directory name. `file`
depicts the name of a file in the directory. Several files can be given, in
which case the server returns the first it finds, for example:
```erlang
{directory_index, ["index.html", "welcome.html"]}
```
Access to http://your.server.org/docs/ would return
http://your.server.org/docs/index.html or
http://your.server.org/docs/welcome.html if index.html does not exist.
[](){: #props_cgi }
### CGI Properties - Requires mod_cgi
> #### Note {: .info }
> `mod_cgi` and `mod_actions` are deprecated since OTP 29 and will be removed in OTP 30.
> Use `mod_esi` instead for dynamic page generation.
>
- [](){: #prop_script_alias } **`{script_alias, {Alias, RealName}}`**
`Alias = string()` and `RealName = string()`. Have the same behavior as
property `alias`, except that they also mark the target directory as
containing CGI scripts. URLs with a path beginning with url-path are mapped to
scripts beginning with directory-filename, for example:
```text
{script_alias, {"/cgi-bin/", "/web/cgi-bin/"}}
```
Access to http://your.server.org/cgi-bin/foo would cause the server to run the
script /web/cgi-bin/foo.
> #### Note {: .info }
>
> When using `script_alias` with directory-based authentication
> (see [`directory`](`m:httpd#prop_dri`)), ensure that authentication
> rules reference the actual filesystem path (RealName), not the URL path (Alias).
> The server correctly resolves script_alias paths for authentication checks.
>
- [](){: #prop_script_re_write } **`{script_re_write, {Re, Replacement}}`**
`Re = string()` and `Replacement = string()`. Have the same behavior as
property `re_write`, except that they also mark the target directory as
containing CGI scripts. URLs with a path beginning with url-path are mapped to
scripts beginning with directory-filename, for example:
```text
{script_re_write, {"^/cgi-bin/(\\d+)/", "/web/\\1/cgi-bin/"}}
```
Access to http://your.server.org/cgi-bin/17/foo would cause the server to run
the script /web/17/cgi-bin/foo.
- [](){: #prop_script_nocache } **`{script_nocache, boolean()}`**
If `script_nocache` is set to `true`, the HTTP server by default adds the
header fields necessary to prevent proxies from caching the page. Generally
this is preferred. Default to `false`.
- [](){: #prop_script_timeout } **`{script_timeout, integer()}`**
The time in seconds the web server waits between each chunk of data from the
script. If the CGI script does not deliver any data before the timeout, the
connection to the client is closed. Default is `15`.
- [](){: #prop_action } **`{action, {MimeType, CgiScript}}`** - requires `mod_actions`
`MimeType = string()` and `CgiScript = string()`. `action` adds an action
activating a CGI script whenever a file of a certain MIME type is requested.
It propagates the URL and file path of the requested document using the
standard CGI PATH_INFO and PATH_TRANSLATED environment variables.
Example:
```text
{action, {"text/plain", "/cgi-bin/log_and_deliver_text"}}
```
> #### Note {: .info }
> `mod_cgi` and `mod_actions` are deprecated since OTP 29 and will be removed in OTP 30.
> Use `mod_esi` instead for dynamic page generation.
>
- [](){: #prop_script } **`{script, {Method, CgiScript}}`** - requires `mod_actions`
`Method = string()` and `CgiScript = string()`. `script` adds an action
activating a CGI script whenever a file is requested using a certain HTTP
method. The method is either GET or POST, as defined in
[RFC 1945](http://www.ietf.org/rfc/rfc1945.txt). It propagates the URL and
file path of the requested document using the standard CGI PATH_INFO and
PATH_TRANSLATED environment variables.
Example:
```erlang
{script, {"PUT", "/cgi-bin/put"}}
```
> #### Note {: .info }
> `mod_cgi` and `mod_actions` are deprecated since OTP 29 and will be removed in OTP 30.
> Use `mod_esi` instead for dynamic page generation.
>
[](){: #props_esi }
### ESI Properties - Requires mod_esi
- [](){: #prop_esi_alias } **`{erl_script_alias, {URLPath, [AllowedModule]}}`**
`URLPath = string()` and `AllowedModule = atom()`. `erl_script_alias` marks
all URLs matching url-path as erl scheme scripts. A matching URL is mapped
into a specific module and function, for example:
```erlang
{erl_script_alias, {"/cgi-bin/example", [httpd_example]}}
```
A request to http://your.server.org/cgi-bin/example/httpd_example:yahoo would
refer to httpd_example:yahoo/3 or, if that does not exist,
httpd_example:yahoo/2 and http://your.server.org/cgi-bin/example/other:yahoo
would not be allowed to execute.
- [](){: #prop_esi_nocache } **`{erl_script_nocache, boolean()}`**
If `erl_script_nocache` is set to `true`, the server adds HTTP header fields
preventing proxies from caching the page. This is generally a good idea for
dynamic content, as the content often varies between each request. Default is
`false`.
- [](){: #prop_esi_timeout } **`{erl_script_timeout, integer()}`**
If `erl_script_timeout` sets the time in seconds the server waits between each
chunk of data to be delivered through `mod_esi:deliver/2`. Default is `15`.
This is only relevant for scripts that use the erl scheme.
[](){: #props_log }
### Log Properties - Requires mod_log
- [](){: #prop_elog } **`{error_log, path()}`**
Defines the filename of the error log file to be used to log server errors. If
the filename does not begin with a slash (/), it is assumed to be relative to
the `server_root`.
- [](){: #prop_slog } **`{security_log, path()}`**
Defines the filename of the access log file to be used to log security events.
If the filename does not begin with a slash (/), it is assumed to be relative
to the `server_root`.
- [](){: #prop_tlog } **`{transfer_log, path()}`**
Defines the filename of the access log file to be used to log incoming
requests. If the filename does not begin with a slash (/), it is assumed to be
relative to the `server_root`.
[](){: #props_dlog }
### Disk Log Properties - Requires mod_disk_log
- [](){: #prop_dlog_format } **`{disk_log_format, internal | external}`**
Defines the file format of the log files. See `disk_log` for details. If the
internal file format is used, the log file is repaired after a crash. When a
log file is repaired, data can disappear. When the external file format is
used, `httpd` does not start if the log file is broken. Default is `external`.
- [](){: #prop_edlog } **`{error_disk_log, path()}`**
Defines the filename of the (`m:disk_log`) error log file to be used to log
server errors. If the filename does not begin with a slash (/), it is assumed
to be relative to the `server_root`.
- [](){: #prop_edlog_size } **`{error_disk_log_size, {MaxBytes, MaxFiles}}`**
`MaxBytes = integer()` and `MaxFiles = integer()`. Defines the properties of
the (`m:disk_log`) error log file. This file is of type wrap log and max bytes
is written to each file and max files is used before the first file is
truncated and reused.
- [](){: #prop_sdlog } **`{security_disk_log, path()}`**
Defines the filename of the (`m:disk_log`) access log file logging incoming
security events, that is, authenticated requests. If the filename does not
begin with a slash (/), it is assumed to be relative to the `server_root`.
- [](){: #prop_sdlog_size } **`{security_disk_log_size, {MaxBytes, MaxFiles}}`**
`MaxBytes = integer()` and `MaxFiles = integer()`. Defines the properties of
the `m:disk_log` access log file. This file is of type wrap log and max bytes
is written to each file and max files is used before the first file is
truncated and reused.
- [](){: #prop_tdlog } **`{transfer_disk_log, path()}`**
Defines the filename of the (`m:disk_log`) access log file logging incoming
requests. If the filename does not begin with a slash (/), it is assumed to be
relative to the `server_root`.
- [](){: #prop_tdlog_size } **`{transfer_disk_log_size, {MaxBytes, MaxFiles}}`**
`MaxBytes = integer()` and `MaxFiles = integer()`. Defines the properties of
the `m:disk_log` access log file. This file is of type wrap log and max bytes
is written to each file and max files is used before the first file is
truncated and reused.
[](){: #props_auth }
### Authentication Properties - Requires mod_auth
[](){: #prop_dri }
```erlang
{directory, {path(), [{property(), term()}]}}
```
[](){: #props_dir }
The properties for directories are as follows:
- [](){: #prop_allow_from } **`{allow_from, all | [RegxpHostString]}`**
Defines a set of hosts to be granted access to a given directory, for example:
```erlang
{allow_from, ["123.34.56.11", "150.100.23"]}
```
The host `123.34.56.11` and all machines on the `150.100.23` subnet are
allowed access.
- [](){: #prop_deny_from } **`{deny_from, all | [RegxpHostString]}`**
Defines a set of hosts to be denied access to a given directory, for example:
```text
{deny_from, ["123.34.56.11", "150.100.23"]}
```
The host `123.34.56.11` and all machines on the `150.100.23` subnet are not
allowed access.
- [](){: #prop_auth_type } **`{auth_type, plain | dets | mnesia}`**
Sets the type of authentication database that is used for the directory. The
key difference between the different methods is that dynamic data can be saved
when Mnesia and Dets are used.
- [](){: #prop_auth_user_file } **`{auth_user_file, path()}`**
Sets the name of a file containing the list of users and passwords for user
authentication. The filename can be either absolute or relative to the
`server_root`. If using the plain storage method, this file is a plain text
file where each line contains a username followed by a colon, followed by the
non-encrypted password. If usernames are duplicated, the behavior is
undefined.
Example:
```text
ragnar:s7Xxv7
edward:wwjau8
```
If the Dets storage method is used, the user database is maintained by Dets
and must not be edited by hand. Use the API functions in module `mod_auth` to
create/edit the user database. This directive is ignored if the Mnesia storage
method is used. For security reasons, ensure that `auth_user_file` is stored
outside the document tree of the web server. If it is placed in the directory
that it protects, clients can download it.
- [](){: #prop_auth_group_file } **`{auth_group_file, path()}`**
Sets the name of a file containing the list of user groups for user
authentication. The filename can be either absolute or relative to the
`server_root`. If the plain storage method is used, the group file is a plain
text file, where each line contains a group name followed by a colon, followed
by the members usernames separated by spaces.
Example:
```text
group1: bob joe ante
```
If the Dets storage method is used, the group database is maintained by Dets
and must not be edited by hand. Use the API for module `mod_auth` to
create/edit the group database. This directive is ignored if the Mnesia
storage method is used. For security reasons, ensure that the
`auth_group_file` is stored outside the document tree of the web server. If it
is placed in the directory that it protects, clients can download it.
- [](){: #prop_auth_name } **`{auth_name, string()}`**
Sets the name of the authorization realm (auth-domain) for a directory. This
string informs the client about which username and password to use.
- [](){: #prop_auth_access_passwd } **`{auth_access_password, string()}`**
If set to other than `"NoPassword"`, the password is required for all API calls.
If the password is set to `"DummyPassword"`, the password must be changed before
any other API calls. To secure the authenticating data, the password must be
changed after the web server is started. Otherwise it is written in clear text
in the configuration file.
- [](){: #prop_req_user } **`{require_user, [string()]}`**
Defines users to grant access to a given directory using a secret password.
- [](){: #prop_req_grp } **`{require_group, [string()]}`**
Defines users to grant access to a given directory using a secret password.
[](){: #props_sec }
### Security Properties - Requires mod_security
[](){: #prop_sec_dir }
```erlang
{security_directory, {path(), [{property(), term()}]}}
```
[](){: #props_sdir }
The properties for the security directories are as follows:
- [](){: #prop_data_file } **`{data_file, path()}`**
Name of the security data file. The filename can either be absolute or
relative to the `server_root`. This file is used to store persistent data for
module `mod_security`.
- [](){: #prop_max_retries } **`{max_retries, integer()}`**
Specifies the maximum number of attempts to authenticate a user before the
user is blocked out. If a user successfully authenticates while blocked, the
user receives a 403 (Forbidden) response from the server. If the user makes a
failed attempt while blocked, the server returns 401 (Unauthorized), for
security reasons. Default is `3`. Can be set to infinity.
- [](){: #prop_block_time } **`{block_time, integer()}`**
Specifies the number of minutes a user is blocked. After this time has passed,
the user automatically regains access. Default is `60`.
- [](){: #prop_fail_exp_time } **`{fail_expire_time, integer()}`**
Specifies the number of minutes a failed user authentication is remembered. If
a user authenticates after this time has passed, the previous failed
authentications are forgotten. Default is `30`.
- [](){: #prop_auth_timeout } **`{auth_timeout, integer()}`**
Specifies the number of seconds a successful user authentication is
remembered. After this time has passed, the authentication is no longer
reported. Default is `30`.
## Web server API data types
The Erlang web server API data types are as follows:
```erlang
ModData = #mod{}
-record(mod, {
data = [],
socket_type = ip_comm,
socket,
config_db,
method,
absolute_uri,
request_uri,
http_version,
request_line,
parsed_header = [],
entity_body,
connection
}).
```
To access the record in your callback-module use:
```erlang
-include_lib("inets/include/httpd.hrl").
```
The fields of record `mod` have the following meaning:
- **`data`** - Type `[{InteractionKey,InteractionValue}]` is used to propagate
data between modules. Depicted `interaction_data()` in function type
declarations.
- **`socket_type`** - `socket_type()` indicates whether it is an IP socket or an
`ssl` socket.
- **`socket`** - The socket, in format `ip_comm` or `ssl`, depending on
`socket_type`.
- **`config_db`** - The config file directives stored as key-value tuples in an
ETS table. Depicted `config_db()` in function type declarations.
- **`method`** - Type `"GET" | "POST" | "HEAD" | "TRACE"`, that is, the HTTP
method.
- **`absolute_uri`** - If the request is an HTTP/1.1 request, the URI can be in
the absolute URI format. In that case, `httpd` saves the absolute URI in this
field. An Example of an absolute URI is
`"http://ServerName:Part/cgi-bin/find.pl?person=jocke"`
- **`request_uri`** - The `Request-URI` as defined in
[RFC 1945](http://www.ietf.org/rfc/rfc1945.txt), for example,
`"/cgi-bin/find.pl?person=jocke"`.
- **`http_version`** - The `HTTP` version of the request, that is, "HTTP/1.0",
or "HTTP/1.1".
- **`request_line`** - The `Request-Line` as defined
in[RFC 1945](http://www.ietf.org/rfc/rfc1945.txt), for example,
`"GET /cgi-bin/find.pl?person=jocke HTTP/1.0"`.
- **`parsed_header`** - Type `[{HeaderKey,HeaderValue}]`. `parsed_header`
contains all HTTP header fields from the HTTP request stored in a list as
key-value tuples. See [RFC 2616](http://www.ietf.org/rfc/rfc2616.txt) for a
listing of all header fields. For example, the date field is stored as
`{"date","Wed, 15 Oct 1997 14:35:17 GMT"}`. RFC 2616 defines that HTTP is a
case-insensitive protocol and the header fields can be in lower case or upper
case. `httpd` ensures that all header field names are in lower case.
- **`entity_body`** - The `entity-Body` as defined in
[RFC 2616](http://www.ietf.org/rfc/rfc2616.txt), for example, data sent from a
CGI script using the POST method.
- **`connection`** - `true | false`. If set to `true`, the connection to the
client is a persistent connection and is not closed when the request is
served.
### See also
[RFC 2616](http://www.ietf.org/rfc/rfc2616.txt), `m:inets`, `m:ssl`
""".
-compile([{nowarn_possibly_unsafe_function, {file, consult, 1}}]).
-behaviour(inets_service).
-include("httpd_internal.hrl").
%% Behavior callbacks
-export([
start_standalone/1,
start_service/1,
stop_service/1,
services/0,
service_info/1
]).
%% API
-export([
parse_query/1,
reload_config/2,
info/1,
info/2,
info/3,
info/4
]).
-export_type([socket_type/0]).
%% Command line interface
-export([start/1, serve/1]).
-deprecated({parse_query, 1,
"use uri_string:dissect_query/1 instead"}).
%%%========================================================================
%%% Types
%%%========================================================================
-type property() :: atom().
-type socket_type() :: ip_comm | ssl.
%%%========================================================================
%%% Callbacks
%%%========================================================================
-doc """
When a valid request reaches `httpd`, it calls [`do/1`](`c:do/1`) in each
module, defined by the configuration option of `Module`. The function can
generate data for other modules or a response that can be sent back to the
client.
The field `data` in `ModData` is a list. This list is the list returned from the
last call to [`do/1`](`c:do/1`).
`Body` is the body of the HTTP response that is sent back to the client. An
appropriate header is appended to the message. `StatusCode` is the status code
of the response, see [RFC 2616](http://www.ietf.org/rfc/rfc2616.txt) for the
appropriate values.
`Head` is a key value list of HTTP header fields. The server constructs an HTTP
header from this data. See [RFC 2616](http://www.ietf.org/rfc/rfc2616.txt) for
the appropriate value for each header field. If the client is an HTTP/1.0
client, the server filters the list so that only HTTP/1.0 header fields are sent
back to the client.
If `Body` is returned and equal to `{Fun,Arg}`, the web server tries
[`apply/2`](`apply/2`) on `Fun` with `Arg` as argument. The web server expects
that the fun either returns a list `(Body)` that is an HTTP response, or the
atom `sent` if the HTTP response is sent back to the client. If `close` is
returned from the fun, something has gone wrong and the server signals this to
the client by closing the connection.
> #### Note {: .info }
>
> It is strongly advised to use NewDataFormat in the return value of `do/1`
> as it relies on a newer mechanism for parsing and sending headers,
> provides more accurate status codes, and supports a wider range of Body formats.
>
""".
-doc(#{group => <<"ERLANG WEB SERVER API CALLBACK FUNCTIONS">>}).
-callback do(ModData) -> {proceed, OldData} | {proceed, NewData} | {break, NewData} | done when
ModData :: [{data,NewData} | {'Body', Body} | {'Head',Head}],
OldData :: list(),
NewData :: [{response, NewDataCompatFormat}] | [{response, NewDataFormat}],
NewDataCompatFormat :: {StatusCode, Body},
NewDataFormat :: {response, Head, Body} | {already_sent, StatusCode, Size},
StatusCode :: integer(),
Size :: non_neg_integer(),
Body :: iolist() | nobody | {Fun, FunArg},
Head :: [HeaderOption] | {Key, Value},
HeaderOption :: {Option, Value} | {code, StatusCode},
Option :: accept_ranges | allow,
Key :: atom() | string(),
Value :: string(),
FunArg :: [term()],
Fun :: fun((FunArg) -> sent | close | Body).
-doc """
When `httpd` is shut down, it tries to execute [`remove/1`](`c:remove/1`) in
each Erlang web server callback module. The programmer can use this function to
clean up resources created in the store function.
""".
-doc(#{group => <<"ERLANG WEB SERVER API CALLBACK FUNCTIONS">>}).
-callback remove(ConfigDB) -> ok | {error, Reason} when
ConfigDB :: ets:tid(), Reason :: term().
-doc """
Checks the validity of the configuration options before saving them in the
internal database. This function can also have a side effect, that is, setup of
necessary extra resources implied by the configuration option. It can also
resolve possible dependencies among configuration options by changing the value
of the option. This function only needs clauses for the options implemented by
this particular callback module.
""".
-doc(#{group => <<"ERLANG WEB SERVER API CALLBACK FUNCTIONS">>}).
-callback store({Option, Value}, Config) ->
{ok, {Option, NewValue}} | {error, Reason} when
Option :: property(),
Config :: [{Option, Value}],
Value :: term(),
NewValue :: term(),
Reason :: term().
-optional_callbacks([remove/1, store/2]).
%%%========================================================================
%%% API
%%%========================================================================
-doc """
[`parse_query/1`](`parse_query/1`) parses incoming data to `erl` and `eval`
scripts (see `m:mod_esi`) as defined in the standard URL format, that is, '+'
becomes 'space' and decoding of hexadecimal characters (`%xx`).
""".
-doc(#{group => <<"Web server API help functions">>}).
-spec parse_query(QueryString) -> QueryList | uri_string:error() when
QueryString :: string(),
QueryList :: [{unicode:chardata(), unicode:chardata() | true}].
parse_query(String) ->
uri_string:dissect_query(String).
-doc """
Reloads the HTTP server configuration without restarting the server. Incoming
requests are answered with a temporary down message during the reload time.
> #### Note {: .info }
>
> Available properties are the same as the start options of the server, but the
> properties `bind_address` and `port` cannot be changed.
If mode is disturbing, the server is blocked forcefully, all ongoing requests
terminates, and the reload starts immediately. If mode is non-disturbing, no new
connections are accepted, but ongoing requests are allowed to complete before
the reload is done.
""".
-spec reload_config(Config, Mode) -> ok | {error, Reason} | no_return() when
Config :: file:name_all() | [{Option, Value}],
Mode :: non_disturbing | disturbing | blocked,
Option :: atom(),
Value :: term(),
Reason :: term().
reload_config(Config = [Value| _], Mode) when is_tuple(Value) ->
do_reload_config(Config, Mode);
reload_config(ConfigFile, Mode) ->
try file:consult(ConfigFile) of
{ok, [PropList]} ->
%% Erlang terms format
do_reload_config(PropList, Mode)
catch
exit:_ ->
throw({error, {could_not_consult_proplist_file, ConfigFile}})
end.
-doc(#{equiv => info/2}).
-spec info(Pid) -> HttpInformation when
Pid :: pid(),
Path :: file:name_all(),
HttpInformation :: [CommonOption]
| [CommunicationOption]
| [ModOption]
| [LimitOption]
| [AdminOption],
CommonOption :: {port, non_neg_integer()}
| {server_name, string()}
| {server_root, Path}