@@ -4,15 +4,15 @@ Exporters and services instrumented with the Exporter Toolkit share the same
44web configuration file format. This is * experimental* and might change in the
55future.
66
7- To specify which web configuration file to load, use the --web.config.file flag.
7+ To specify which web configuration file to load, use the ` --web.config.file ` flag.
88
99The file is written in [ YAML format] ( https://en.wikipedia.org/wiki/YAML ) ,
1010defined by the scheme described below.
1111Brackets indicate that a parameter is optional. For non-list parameters the
1212value is set to the specified default.
1313
1414The file is read upon every http request, such as any change in the
15- configuration and the certificates is picked up immediately.
15+ configuration, so the certificates are picked up immediately.
1616
1717Generic placeholders are defined as follows:
1818
@@ -86,10 +86,10 @@ which will look something like:
8686` $2y$10$X0h1gDsPszWURQaxFh.zoubFi6DXncSjhoQNJgRrnGs7EsimhC7zG `
8787
8888The cost (10 in the example) influences the time it takes for computing the
89- hash. A higher cost will en up slowing down the authentication process.
90- Depending on the machine, a cost of 10 will take about ~ 70ms where a cost of
91- 18 can take up to a few seconds. That hash will be computed on every
92- password-protected request.
89+ hash. A higher cost will end up slowing down the authentication process.
90+ Depending on the machine, a cost of 10 will take about ~ 70ms, whereas a cost of
91+ 18 can take up to a few seconds. That hash will be computed on the first
92+ authenticated HTTP request and then cached .
9393
9494## Performance
9595
0 commit comments