[FFmpeg-trac] #2129(avformat:new): no_proxy environment variable implemented wrong

[FFmpeg]

#2129: no_proxy environment variable implemented wrong
------------------------------------+------------------------------------
             Reporter:  divVerent   |                    Owner:
                 Type:  defect      |                   Status:  new
             Priority:  normal      |                Component:  avformat
              Version:  git-master  |               Resolution:
             Keywords:  http        |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+------------------------------------

Comment (by divVerent):

 Also, in typical setups, one plays videos from external sources more
 likely than from internal sources.

 Also, typically, no_proxy lists the internal networks you do not
 need/want/can use a proxy for, and anything not listed there is the "big
 and wide internet", from where the videos come.

 So, NOT supporting no_proxy would actually do less damage than this "half"
 support for it...

 As for an authoritative specification, I didn't find any yet, but
 generally the following things seem to be common between most
 implementations:

 - It is a comma separated list of domain names; whitespace after the
 commas is allowed.
 - Wildcards are allowed and match one or more DNS labels. So, listing
 "*.example.org" excludes anything ending with .example.org, even multiple
 labels. As a special case, "*" excludes all.
 - I did not check whether *.example.org tends to more likely include
 example.org itself or not.
 - IP addresses tend to be matched the same way as DNS labels. So
 "192.168.*" matches 192.168.0.1 but also 192.168.foo.bar.com. Many
 implementations also support network mask entries, like "192.168.0.0/16".
 - Many implementations also allow adding a port to entries, like in
 "example.org:1234". When no port is specified, all ports are to be
 matched.
 - I am not aware of a common library or a standard to do all this.

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2129#comment:1>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker