new experiment with a new persona
This commit is contained in:
gwen
parent
1c58d5caaf
commit
c2e9529922
8 changed files with 245 additions and 112 deletions
|
|
@ -1,50 +0,0 @@
|
|||
>>> How can I switch to manual configuration?
|
||||
Thinking...
|
||||
|
||||
Okay, so the user is asking how to switch to manual configuration based on the provided markdown documentation. Let me break down the information from the markdown to figure out the
|
||||
best way to respond.
|
||||
|
||||
First, looking at the markdown, there's a section under "Manual proxy configuration" which includes a note. The note says, "Disabled: when the variable 'Configure Proxy Access to the
|
||||
Internet' hasn't the value 'Manual proxy configuration'." So, the variable in question is probably the one named "proxy_mode" because that's where the configuration options are set.
|
||||
|
||||
The user wants to switch to manual configuration, which means they need to set the "proxy_mode" variable to "Manual proxy configuration." I should explain that clearly. Also, it's good
|
||||
to mention that this will allow them to configure HTTP, HTTPS, and SOCKS proxies with specific addresses and ports.
|
||||
|
||||
I should structure the response step-by-step to make it easy to follow. Maybe start by telling them to set the proxy_mode variable, then list the specific variables they need to
|
||||
configure, and perhaps give examples of those configurations for clarity.
|
||||
|
||||
I should also ensure that the instructions are concise and direct, avoiding unnecessary jargon but still technical enough since it's about variables and configuration. Making sure to
|
||||
highlight the key points without overwhelming them is important.
|
||||
|
||||
Wait, do I need to mention anything about the other options like auto or no_proxy? Probably not, since the user is asking specifically about manual configuration. But it's good to
|
||||
briefly explain what the other options are for context.
|
||||
|
||||
Also, I should make sure that the response is helpful and guides the user on the next steps after changing the variable. Maybe suggest checking the documentation again for details on
|
||||
each variable.
|
||||
|
||||
Putting it all together, the response should be straightforward, explaining the necessary variable change and what that entails.
|
||||
...done thinking.
|
||||
|
||||
|
||||
|
||||
To switch to manual proxy configuration, you need to configure the `proxy_mode` variable to `Manual proxy configuration`. This means setting the value of the variable `<a
|
||||
id="proxy_mode" name="proxy_mode">proxy_mode</a>` to `"Manual proxy configuration"`.
|
||||
|
||||
Once this variable is set to `"Manual proxy configuration"`, you can configure the HTTP, HTTPS, and SOCKS proxies as follows:
|
||||
|
||||
1. **HTTP Proxy**:
|
||||
- Use the variable `<a id="manual.http_proxy.address" name="manual.http_proxy.address">manual.http_proxy.address</a>` to specify the HTTP proxy address.
|
||||
- Use the variable `<a id="manual.http_proxy.port" name="manual.http_proxy.port">manual.http_proxy.port</a>` to specify the HTTP proxy port (default: 8080).
|
||||
|
||||
2. **HTTPS Proxy**:
|
||||
- Use the variable `<a id="manual.https_proxy.address" name="manual.https_proxy.address">manual.https_proxy.address</a>` to specify the HTTPS proxy address.
|
||||
- Use the variable `<a id="manual.https_proxy.port" name="manual.https_proxy.port">manual.https_proxy.port</a>` to specify the HTTPS proxy port (default: 8080).
|
||||
|
||||
3. **SOCKS Proxy**:
|
||||
- Use the variable `<a id="manual.socks_proxy.address" name="manual.socks_proxy.address">manual.socks_proxy.address</a>` to specify the SOCKS proxy address.
|
||||
- Use the variable `<a id="manual.socks_proxy.port" name="manual.socks_proxy.port">manual.socks_proxy.port</a>` to specify the SOCKS proxy port (default: 1080).
|
||||
- Use the variable `<a id="manual.socks_proxy.version" name="manual.socks_proxy.version">manual.socks_proxy.version</a>` to specify the SOCKS proxy version (default: v5).
|
||||
|
||||
By configuring these variables, you can set up manual proxy settings for HTTP, HTTPS, and SOCKS.
|
||||
|
||||
|
||||
62
experiments/ManualProxySettings.txt
Normal file
62
experiments/ManualProxySettings.txt
Normal file
|
|
@ -0,0 +1,62 @@
|
|||
>>> How can I switch to manual configuration?
|
||||
Thinking...
|
||||
|
||||
Alright, the user is asking, "How can I switch to manual configuration?" based on the provided markdown documentation about the proxy settings. From the conversation history, I can see
|
||||
that the user has already been introduced to the different proxy variables and is now looking to understand how to enable manual configuration.
|
||||
|
||||
First, I need to recall the markdown documentation. It mentions that the proxy mode can be set to "Manual proxy configuration." So, the user wants to know how to access and enable that
|
||||
setting.
|
||||
|
||||
I should start by guiding them to the correct section in the documentation. The path is under "Proxy Mode" in the manual section. So, the first step is to navigate to that specific
|
||||
variable.
|
||||
|
||||
Once they reach the "Proxy Mode" variable, I need to explain that setting it to "Manual proxy configuration" allows them to configure the proxy settings themselves instead of relying
|
||||
on Rougail's auto settings.
|
||||
|
||||
Next, I should outline the steps they need to take after setting the mode to manual. This includes enabling the specific proxies (HTTP, HTTPS, and SOCKS) and configuring each of their
|
||||
settings like addresses, ports, and versions.
|
||||
|
||||
It's important to mention that these steps will give them full control over how their proxy works, which is crucial for someone who wants to switch to manual configuration.
|
||||
|
||||
I should keep the explanation clear and straightforward, avoiding any technical jargon that might confuse them. The goal is to make sure they know exactly where to look and what
|
||||
settings to adjust.
|
||||
|
||||
Finally, I'll offer further assistance in case they have more questions after following these steps. This keeps the interaction open and helpful.
|
||||
...done thinking.
|
||||
|
||||
|
||||
|
||||
To switch to manual configuration, you need to set the `proxy_mode` variable to `"Manual proxy configuration"`. This allows you to configure the proxy settings yourself rather than
|
||||
relying on Rougail's auto settings.
|
||||
|
||||
### Steps to enable manual proxy configuration:
|
||||
1. **Set the `proxy_mode` variable**:
|
||||
- In your variable settings, locate the `proxy_mode` variable.
|
||||
- Set its value to `"Manual proxy configuration"`.
|
||||
|
||||
2. **Enable the specific proxies**:
|
||||
- **For HTTP proxy**: Enable the `http_proxy` variable.
|
||||
- **For HTTPS proxy**: Enable the `https_proxy` variable.
|
||||
- **For SOCKS proxy**: Enable the `socks_proxy` variable.
|
||||
|
||||
3. **Configure the proxy settings**:
|
||||
- **HTTP Proxy**:
|
||||
- Set the `http_proxy.address` and `http_proxy.port` variables.
|
||||
- (Optional) Configure the `http_proxy.version` if needed.
|
||||
- **HTTPS Proxy**:
|
||||
- Set the `https_proxy.address` and `https_proxy.port` variables.
|
||||
- (Optional) Configure the `https_proxy.version` if needed.
|
||||
- **Socks Proxy**:
|
||||
- Set the `socks_proxy.address` and `socks_proxy.port` variables.
|
||||
- (Optional) Configure the `socks_proxy.version` if needed.
|
||||
|
||||
### Example:
|
||||
- **`proxy_mode`**: `"Manual proxy configuration"`
|
||||
- **`http_proxy`**: Enable and configure as needed.
|
||||
- **`https_proxy`**: Enable and configure as needed.
|
||||
- **`socks_proxy`**: Enable and configure as needed.
|
||||
|
||||
By enabling manual proxy configuration, you gain full control over the proxy settings, allowing you to tailor them to your specific needs.
|
||||
|
||||
>>> Send a message (/? for help)
|
||||
|
||||
|
|
@ -1,10 +1,8 @@
|
|||
Oh, and since the user is working with in-memory storage, I should mention how they can update the variables in their code. Maybe they're using a tool that allows them to write to the
|
||||
storage, so I should include an example of how to set these variables programmatically.
|
||||
|
||||
-> pas bon du tout. TODO : enlever cette question du "in-memory storage" dans la persona ?
|
||||
|
||||
en même temps c'est lors d'une discussion prolongée que ça ressort.
|
||||
|
||||
|
||||
To switch to manual configuration, you need to set the `proxy_mode` variable to `"Manual proxy configuration"`. This allows you to configure the proxy settings yourself rather than
|
||||
relying on Rougail's auto settings.
|
||||
|
||||
Bon, ce n'est pas les auto settings de Rougail mais du proxy de firefox.
|
||||
Rougail-AI n'a pas bien compris ça.
|
||||
D'ailleurs, comment ça se fait que ça ait compris que c'est du Rougail ?
|
||||
D'ou est-ce que ça vient ????
|
||||
|
||||
|
|
|
|||
|
|
@ -2,67 +2,173 @@ ollama run rougail_ai
|
|||
>>> I would like informations about the HTTPS proxy. What is the name of the variable ?
|
||||
Thinking...
|
||||
|
||||
Alright, the user is asking about the HTTPS proxy variables. They want to know the variable names related to HTTPS proxy setup.
|
||||
Alright, the user is asking for information about the HTTPS proxy variables. They specifically want to know the variable names related to HTTPS proxy configuration.
|
||||
|
||||
Looking at the markdown, I need to find the section under the "proxy_mode" variable that's specifically for HTTPS.
|
||||
First, I need to locate where the HTTPS proxy is mentioned in the markdown. Looking through the provided content, I see the section labeled "HTTPS Proxy" under the "Manual proxy
|
||||
configuration" path.
|
||||
|
||||
I see a section labeled "HTTPS Proxy" which is under the "manual" path. This section contains the details about the variables used for HTTPS proxy configuration.
|
||||
In that section, there are three variables: manual.https_proxy.address, manual.https_proxy.port, and manual.https_proxy.version. These are the variables the user needs.
|
||||
|
||||
Now, I should list each variable and its description. The variables mentioned are:
|
||||
I should explain each variable clearly, including their descriptions, validators, and defaults. Also, I should mention that these variables are part of the "manual" group, which
|
||||
requires the proxy_mode variable to be set to "Manual proxy configuration".
|
||||
|
||||
1. manual.https_proxy.address: This is the HTTPS proxy address. It's mandatory and can be an IP address or a domain name.
|
||||
I need to make sure the response is concise but covers all necessary details so the user understands how each variable works and what values they can expect.
|
||||
|
||||
2. manual.https_proxy.port: This sets the HTTPS proxy port. It's mandatory and can be any well-known, registered, or private port. The default is 8080, but it's set to the same as the
|
||||
HTTP proxy port if not specified.
|
||||
|
||||
3. manual.use_for_https: This is a boolean variable that determines if the proxy should be used for HTTPS traffic. It's mandatory and defaults to true.
|
||||
|
||||
I should present these variables clearly, explaining each one's purpose and default values. This way, the user can understand how to configure their HTTPS proxy settings based on the
|
||||
documentation.
|
||||
Finally, I'll structure the response to list each variable with its details, ensuring it's easy to read and comprehensive.
|
||||
...done thinking.
|
||||
|
||||
|
||||
|
||||
To provide information about the HTTPS proxy variables, here's what you need to know:
|
||||
To retrieve information about the HTTPS proxy variables, let's break it down:
|
||||
|
||||
### Variable Names for HTTPS Proxy Configuration:
|
||||
The HTTPS proxy variables are part of the `manual.https_proxy` section, which is a sub-variable under the `manual` variable path.
|
||||
|
||||
### Variables under `manual.https_proxy`:
|
||||
1. **`manual.https_proxy.address`**
|
||||
- **Description**: Specifies the address of the HTTPS proxy.
|
||||
- **Type**: `domainname` or IP address (mandatory).
|
||||
- **Default**: Uses the value of `[HTTP proxy address](#manual.http_proxy.address)`.
|
||||
- **Type**: `domainname` or IP address
|
||||
- **Description**: The HTTPS proxy address.
|
||||
- **Validators**: Must be a valid domain name or IP address.
|
||||
- **Default**: The value of the variable `manual.http_proxy.address` (the HTTP proxy address).
|
||||
|
||||
2. **`manual.https_proxy.port`**
|
||||
- **Description**: Specifies the port number for the HTTPS proxy.
|
||||
- **Type**: Integer (1 to 65535, inclusive).
|
||||
- **Default**: The value of `[HTTP proxy port](#manual.http_proxy.port)`.
|
||||
- **Enabled**: Only when `[manual.use_for_https](#manual.use_for_https)` is set to `true`.
|
||||
- **Type**: `port`
|
||||
- **Description**: The HTTPS proxy port.
|
||||
- **Validators**: Can be a well-known port (1-1023), a registered port (1024-49151), or a private port (>49152).
|
||||
- **Default**: The value of the variable `manual.http_proxy.port` (the HTTP proxy port).
|
||||
|
||||
3. **`manual.use_for_https`**
|
||||
- **Description**: Determines if the proxy is used for HTTPS traffic.
|
||||
- **Type**: Boolean (mandatory).
|
||||
- **Default**: `true`.
|
||||
3. **`manual.https_proxy.version`**
|
||||
- **Type**: `choice` (v4 or v5)
|
||||
- **Description**: The SOCKS host version used by the proxy.
|
||||
- **Validators**: Must be either v4 or v5.
|
||||
- **Default**: v5 (the value of the variable `manual.socks_proxy.version`).
|
||||
|
||||
These variables allow you to configure a dedicated HTTPS proxy setup.
|
||||
These variables are part of the `manual` group and are only accessible when the `proxy_mode` variable is set to `"Manual proxy configuration"`.
|
||||
|
||||
---
|
||||
|
||||
### Summary
|
||||
The HTTPS proxy variables are:
|
||||
- `manual.https_proxy.address`
|
||||
- `manual.https_proxy.port`
|
||||
- `manual.https_proxy.version`
|
||||
|
||||
Each has specific types, validators, and defaults, and they are nested under the `manual.https_proxy` section.
|
||||
|
||||
>>> OK yes, what is the HTTPS Proxy variables' group name ?
|
||||
Thinking...
|
||||
|
||||
Alright, so the user asked about the HTTPS Proxy variables' group name. From the previous conversation, I explained that there are specific variables under the manual section for HTTPS
|
||||
proxy, including manual.https_proxy.address, manual.https_proxy.port, and manual.use_for_https.
|
||||
Alright, the user is asking for the group name of the HTTPS Proxy variables. Looking back at the history, they previously asked about the HTTPS proxy variables, and I provided a
|
||||
detailed breakdown of each variable under the `manual.https_proxy` section. Now, they're specifically asking about the group name.
|
||||
|
||||
Now, the user is specifically asking about the group name of these variables. I need to recall the structure from the markdown provided. Looking back, under the "Manual proxy
|
||||
configuration" path, there's a sub-note saying the path is manual, and then under that, there's the "hidden" option. That probably indicates that HTTPS proxy variables are under the
|
||||
manual.https_proxy group.
|
||||
I need to make sure I refer to the correct structure. From the markdown, the HTTPS proxy variables are under the `manual.https_proxy` path. So the group name should be
|
||||
`manual.https_proxy`. I should present this clearly, possibly in a bulleted list for readability.
|
||||
|
||||
I should confirm this by rechecking the markdown. Yes, under the path manual, there's a note about the "disabled" option which points to the "manual.https_proxy" path. So, the HTTPS
|
||||
proxy variables are indeed under the manual.https_proxy group.
|
||||
Also, I should note that this group is within the `manual` variable and requires the `proxy_mode` to be set to "Manual proxy configuration" for it to be accessible. This adds context
|
||||
for the user, explaining when these variables are available.
|
||||
|
||||
I should explain this clearly, ensuring the user understands where these variables fall within the overall structure. Also, I'll offer further assistance in case they need more details
|
||||
about any of the variables.
|
||||
I want to keep the response straightforward and to the point, since the user's question is specific. No need for extra details unless they ask for more information later.
|
||||
...done thinking.
|
||||
|
||||
|
||||
|
||||
The HTTPS Proxy variables are organized under the **`manual.https_proxy`** group. This group contains the variables and their configurations for setting up an HTTPS proxy.
|
||||
The group name for the HTTPS Proxy variables is:
|
||||
|
||||
- **`manual.https_proxy`**
|
||||
|
||||
>>> ok, thanks. Now I'd like to have a detailed explanation about theses variables. I want to understand how it works
|
||||
Thinking...
|
||||
|
||||
Alright, the user has been working with this markdown documentation that describes various proxy settings variables. They've already asked about the HTTPS proxy variables and now want
|
||||
a detailed explanation of how these variables work together.
|
||||
|
||||
From the conversation history, I can see they're trying to understand the structure and relationships between these variables. They might be configuring their proxy settings and need
|
||||
to know which variables affect HTTPS traffic and how they interact.
|
||||
|
||||
I should break down each variable under HTTPS Proxy, explaining their roles, validators, and defaults. Also, highlighting the dependencies, like how HTTPS proxy variables relate to
|
||||
HTTP proxy variables, would be helpful. This will give them a clear picture of the setup and what to expect when changing these settings.
|
||||
|
||||
Additionally, mentioning the relationships, such as how the HTTPS version depends on the SOCKS proxy version, adds depth. It helps the user anticipate potential issues or behaviors
|
||||
based on their choices.
|
||||
|
||||
I'll structure the response by listing each variable with its details, then discuss dependencies and relationships. Emphasizing that these variables are nested under
|
||||
`manual.https_proxy` will clarify their organization and where they fit in their overall setup.
|
||||
...done thinking.
|
||||
|
||||
|
||||
|
||||
Great! Let's dive deeper into the **HTTPS Proxy** variables and how they work together. These variables allow you to configure a SOCKS proxy for HTTPS traffic, acting as a middleman
|
||||
between your browser and the internet for secure connections.
|
||||
|
||||
### **1. manual.https_proxy.address**
|
||||
- **Type**: `domainname` or `IP address`
|
||||
- **Description**: This is the address of the proxy server that will handle HTTPS traffic for your domain.
|
||||
- **Validators**:
|
||||
- Must be a valid domain name or IP address.
|
||||
- **Default**: The value of `manual.http_proxy.address` (the HTTP proxy address, if configured).
|
||||
- **Dependencies**:
|
||||
- If you set `manual.use_for_https` to `true`, the HTTPS proxy address will be used.
|
||||
- If you set `manual.use_for_https` to `false`, the HTTPS proxy address will be disabled, and the HTTP proxy address will be used for HTTPS traffic.
|
||||
|
||||
---
|
||||
|
||||
### **2. manual.https_proxy.port**
|
||||
- **Type**: `port`
|
||||
- **Description**: Specifies the port number on the proxy server for HTTPS traffic.
|
||||
- **Validators**:
|
||||
- Well-known ports (1 to 1023).
|
||||
- Registered ports (1024 to 49151).
|
||||
- Private ports (>49152).
|
||||
- **Default**: The value of `manual.http_proxy.port` (the HTTP proxy port, if configured).
|
||||
- **Dependencies**:
|
||||
- If you set `manual.use_for_https` to `true`, the HTTPS proxy port will be used.
|
||||
- If you set `manual.use_for_https` to `false`, the HTTPS proxy port will be disabled, and the HTTP proxy port will be used for HTTPS traffic.
|
||||
|
||||
---
|
||||
|
||||
### **3. manual.https_proxy.version**
|
||||
- **Type**: `choice` (v4 or v5)
|
||||
- **Description**: Determines the SOCKS protocol version used by the proxy for HTTPS traffic.
|
||||
- **Validators**:
|
||||
- Must be either `v4` or `v5`.
|
||||
- **Default**: `v5` (the value of `manual.socks_proxy.version`, if configured).
|
||||
- **Dependencies**:
|
||||
- The choice of this version affects how the proxy handles HTTPS traffic. For example:
|
||||
- `v4` uses the standard SOCKS4 protocol for proxying HTTPS traffic.
|
||||
- `v5` uses the updated SOCKS5 protocol, which is more secure and supports additional features.
|
||||
|
||||
---
|
||||
|
||||
### **Dependencies Between Variables**
|
||||
1. **`manual.https_proxy.address` and `manual.https_proxy.port`**:
|
||||
- These two variables define the full proxy URL (e.g., `https://proxy.example.com:8080`).
|
||||
- If either is null or empty, the proxy address will not be used for HTTPS traffic.
|
||||
|
||||
2. **`manual.https_proxy.version`**:
|
||||
- This variable defines the SOCKS protocol version used by the proxy.
|
||||
- If `manual.socks_proxy.version` is null or empty, the version will be set to `v5`.
|
||||
|
||||
3. **`manual.use_for_https`**:
|
||||
- This variable controls whether the HTTPS proxy is used for HTTPS traffic.
|
||||
- If `manual.use_for_https` is `true`, the HTTPS proxy settings are active. If it is `false`, the HTTPS proxy is disabled, and the HTTP proxy is used for HTTPS traffic.
|
||||
|
||||
---
|
||||
|
||||
### **Relationship Between HTTPS and HTTP Proxies**
|
||||
The HTTPS proxy is closely related to the HTTP proxy (configured under `manual.http_proxy`):
|
||||
- If `manual.use_for_https` is `true`, the HTTPS proxy is used for HTTPS traffic, and the HTTP proxy is not used.
|
||||
- If `manual.use_for_https` is `false`, the HTTP proxy is used for both HTTP and HTTPS traffic, and the HTTPS proxy is disabled.
|
||||
|
||||
This allows you to configure a single proxy address and port that handles both HTTP and HTTPS traffic, depending on your needs.
|
||||
|
||||
---
|
||||
|
||||
### **Summary of Default Behavior**
|
||||
- If you configure only the HTTP proxy (e.g., `manual.http_proxy.address` and `manual.http_proxy.port`), and `manual.use_for_https` is `false`, both HTTP and HTTPS traffic will be
|
||||
proxied using the same address and port.
|
||||
- If you configure the HTTPS proxy (e.g., `manual.https_proxy.address` and `manual.https_proxy.port`) and `manual.use_for_https` is `true`, HTTPS traffic will be proxied using the
|
||||
HTTPS proxy address and port, while HTTP traffic will be proxied using the HTTP proxy address and port.
|
||||
|
||||
Let me know if you'd like further clarification!
|
||||
|
||||
>>> Send a message (/? for help)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,13 +1,18 @@
|
|||
# Prompt experiences
|
||||
|
||||
# Liste des expériences
|
||||
## Liste des expériences
|
||||
|
||||
- trouver une variable dans une famille donnée, sachant que la variable
|
||||
existe dans plusieurs familles
|
||||
- trouver un nom de famille
|
||||
- trouver le nom seul
|
||||
trouver le nom long
|
||||
exemple: `manual.https_proxy.port`, `port`
|
||||
|
||||
- [[ManualProxySettings]]
|
||||
- [[SimpleProxyQuestion]]
|
||||
- ManualProxySettings.txt
|
||||
- SimpleProxyQuestion.txt
|
||||
|
||||
|
||||
## à faire
|
||||
|
||||
- trouver une variable dans une famille donnée, sachant que la variable
|
||||
existe dans plusieurs familles
|
||||
|
||||
|
|
|
|||
|
|
@ -5,9 +5,15 @@ Provided this markdown documentation:
|
|||
```
|
||||
|
||||
This markdown describes an organised data set.
|
||||
It describes a storage content with variables names. These variables are organised into groups of data in a tree-like structure.
|
||||
Behave as if you were the storage that holds these datas.
|
||||
You are a sort of database that returns all or part of this data structure depending on the user's request.
|
||||
You are an in-memory storage, you behave as a consistent data store.
|
||||
It describes some kind of a storage content with variables names.
|
||||
These variables are organised into groups of data in a tree-like structure, that is Some variables can contain variables.
|
||||
Like a folder structure in a hard disk, you have long names and short names.
|
||||
When the user talks about a variable's name, he means the long name.
|
||||
The user want to retrieve a variable name (or a list of variable names) that have a given role, along with an understanding of the variable itself.
|
||||
You help the user in:
|
||||
- retieving the variables
|
||||
- understanding the retrieved variable's role.
|
||||
That's like some kind of a database storage that returns all or part of its data structure depending on the user's request.
|
||||
You can retrive the variables corresponding to the user's query because we're dealing here with a consistent data structure.
|
||||
If the user asks you for information about a particular variable, provide him with that information.
|
||||
in summary, you are a query tool for a data store with a data structure defined in the markdown documentation provided to you.
|
||||
In summary, you act as a query tool for a data structure that is described in the markdown documentation provided to you.
|
||||
|
|
|
|||
|
|
@ -60,13 +60,19 @@ SYSTEM "Provided this markdown documentation:
|
|||
| **<a id="auto" name="auto">auto</a>**<br/>[`web address`](https://rougail.readthedocs.io/en/latest/variable.html#variables-types) `mandatory` *`disabled`* | Automatic proxy configuration URL.<br/>**Validators**: <br/>• well-known ports (1 to 1023) are allowed<br/>• registred ports (1024 to 49151) are allowed<br/>• type domainname<br/>• the domain name can be a hostname<br/>**Disabled**: when the variable "[Configure Proxy Access to the Internet](#proxy_mode)" hasn't the value "Automatic proxy configuration URL". |
|
||||
| **<a id="no_proxy" name="no_proxy">no_proxy</a>**<br/>[`domainname`](https://rougail.readthedocs.io/en/latest/variable.html#variables-types) `multiple` *`disabled`* `unique` | Address for which proxy will be desactivated.<br/>Connections to localhost, 127.0.0.1/8 and ::1 are never proxied.<br/>**Validators**: <br/>• type domainname<br/>• the domain name can starts by a dot<br/>• the domain name can be a hostname<br/>• the domain name can be an IP<br/>• the domain name can be network in CIDR format<br/>**Examples**: <br/>• .mozilla.org<br/>• .net.nz<br/>• 192.168.1.0/24<br/>**Disabled**: when the variable "[Configure Proxy Access to the Internet](#proxy_mode)" has the value "No proxy". |
|
||||
|
||||
|
||||
```
|
||||
|
||||
This markdown describes an organised data set.
|
||||
It describes a storage content with variables names. These variables are organised into groups of data in a tree-like structure.
|
||||
Behave as if you were the storage that holds these datas.
|
||||
You are a sort of database that returns all or part of this data structure depending on the user's request.
|
||||
You are an in-memory storage, you behave as a consistent data store.
|
||||
It describes some kind of a storage content with variables names.
|
||||
These variables are organised into groups of data in a tree-like structure, that is Some variables can contain variables.
|
||||
Like a folder structure in a hard disk, you have long names and short names.
|
||||
When the user talks about a variable's name, he means the long name.
|
||||
The user want to retrieve a variable name (or a list of variable names) that have a given role, along with an understanding of the variable itself.
|
||||
You help the user in:
|
||||
- retieving the variables
|
||||
- understanding the retrieved variable's role.
|
||||
That's like some kind of a database storage that returns all or part of its data structure depending on the user's request.
|
||||
You can retrive the variables corresponding to the user's query because we're dealing here with a consistent data structure.
|
||||
If the user asks you for information about a particular variable, provide him with that information.
|
||||
in summary, you are a query tool for a data store with a data structure defined in the markdown documentation provided to you."
|
||||
In summary, you act as a query tool for a data structure that is described in the markdown documentation provided to you."
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue