remarques ok
This commit is contained in:
parent
9d0f0e9ae9
commit
26a9a7edf9
1 changed files with 17 additions and 27 deletions
|
|
@ -617,6 +617,22 @@ Let's have a look at the HTPPS configuration corresponding structure file:
|
|||
variable: __.http_proxy.port
|
||||
...
|
||||
|
||||
We have added a new variable, named `use_for_https` here:
|
||||
|
||||
.. confval:: use_for_https
|
||||
:type: `boolean`
|
||||
:default: `true`
|
||||
|
||||
This is a setting that enables to reuse or not the HTTP proxy configuration for HTTPS
|
||||
|
||||
The variable that drives the hidden/show behavior is the `use_for_https` variable because the `hidden` property has
|
||||
a `variable` target parameter that points to it: `variable: _.use_for_https`.
|
||||
|
||||
.. prerequisites:: Reminder
|
||||
|
||||
The underscore and the point before the variable (`_.use_for_https`) points to the variable that lives in the same
|
||||
family.
|
||||
|
||||
Let's introduce a new Rougail concept here:
|
||||
|
||||
.. glossary::
|
||||
|
|
@ -634,35 +650,9 @@ Let's introduce a new Rougail concept here:
|
|||
It expresses the transition between one situation to another situation,
|
||||
that is, the deeply **statefull** aspects of a data set.
|
||||
|
||||
.. type-along:: A new variable which has the `boolean` type
|
||||
|
||||
The best way to reproduce the `"Also use this HTTP proxy variables for HTTPS"` checkbox in the firefox interface
|
||||
is to add this `use_for_https` variable in our structure file. This boolean variable can reproduce this binary choice option.
|
||||
|
||||
- if the use of the proxy variables for https are the same of the proxy variables for http,
|
||||
that is, if `use_for_https` is true, the https configuration variables are hidden, that's OK.
|
||||
- if the use of the proxy variables for https **are not** the same of the proxy variables for http,
|
||||
we would like to set their default values to the http proxy variables values.
|
||||
|
||||
Do we want to reuse, for the HTTPS mode, the same configuration as for the HTTP mode?
|
||||
Well, it depends on the :term:`context`.
|
||||
|
||||
We have added a new variable, named `use_for_https` here:
|
||||
|
||||
.. confval:: use_for_https
|
||||
:type: `boolean`
|
||||
:default: `true`
|
||||
|
||||
This is a setting that enables to reuse or not the HTTP proxy configuration for HTTPS
|
||||
|
||||
The variable that drives the hidden/show behavior is the `use_for_https` variable because the `hidden` property has
|
||||
a `variable` target parameter that points to it: `variable: _.use_for_https`.
|
||||
|
||||
.. prerequisites:: Reminder
|
||||
|
||||
The underscore and the point before the variable (`_.use_for_https`) points to the variable that lives in the same
|
||||
family.
|
||||
|
||||
.. questions:: Question: how does it work?
|
||||
|
||||
How will this variable drive the reuse of HTTP data to HTTPS data?
|
||||
|
|
@ -729,7 +719,7 @@ We have this output:
|
|||
<span style="color: #5c5cff"> </span><span style="color: #5c5cff"> </span><span style="color: #5c5cff">┗━━ </span>📓 port (HTTPS Port): <span style="color: #ffd700">8080</span>
|
||||
</pre>
|
||||
|
||||
Notice that we have a `use_for_https` new variable, this variable is a `boolean` type, its default value is `True`.
|
||||
Notice that we have this `use_for_https` `boolean` type variable, its default value is `True`.
|
||||
We want to offer the possibility of providing an identical or possibly different proxy configuration for the HTTP and for the HTTPS protocols.
|
||||
|
||||
Here is an example with identical HTTP and HTTPS proxy configuration:
|
||||
|
|
|
|||
Loading…
Reference in a new issue