Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
TLMSP curl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CYBER - Cyber Security
TS 103 523 MSP
TLMSP
TLMSP curl
Commits
991b120e
Commit
991b120e
authored
16 years ago
by
Daniel Stenberg
Browse files
Options
Downloads
Patches
Plain Diff
escape the ' properly
parent
f278d177
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/libcurl/libcurl-tutorial.3
+8
-8
8 additions, 8 deletions
docs/libcurl/libcurl-tutorial.3
with
8 additions
and
8 deletions
docs/libcurl/libcurl-tutorial.3
+
8
−
8
View file @
991b120e
...
...
@@ -667,14 +667,14 @@ default to assume a HTTP proxy):
.IP "Environment Variables"
libcurl automatically checks and uses a set of environment variables to
know
what proxies to use for certain protocols. The names of the variables
are
following an ancient de facto standard and are built up as
"[protocol]_proxy"
(note the lower casing). Which makes the variable
'http_proxy' checked for a
name of a proxy to use when the input URL is
HTTP. Following the same rule,
the variable named 'ftp_proxy' is checked
for FTP URLs. Again, the proxies are always HTTP proxies, the different
names of the variables simply allows
different HTTP proxies to be used.
libcurl automatically checks and uses a set of environment variables to
know
what proxies to use for certain protocols. The names of the variables
are
following an ancient de facto standard and are built up as
"[protocol]_proxy"
(note the lower casing). Which makes the variable
\&'http_proxy' checked for a
name of a proxy to use when the input URL is
HTTP. Following the same rule,
the variable named 'ftp_proxy' is checked
for FTP URLs. Again, the proxies are
always HTTP proxies, the different names of the variables simply allows
different HTTP proxies to be used.
The proxy environment variable contents should be in the format
\&"[protocol://][user:password@]machine[:port]". Where the protocol:// part is
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment