Go to file
openkylin-cibot fc399dd4df No change rebuild. 2024-06-04 09:16:14 +00:00
.github Import Upstream version 0.5.4 2024-04-24 16:42:18 +08:00
data Import Upstream version 0.5.4 2024-04-24 16:42:18 +08:00
debian No change rebuild. 2024-06-04 09:16:14 +00:00
docs Import Upstream version 0.5.4 2024-04-24 16:42:18 +08:00
src Import Upstream version 0.5.4 2024-04-24 16:42:18 +08:00
subprojects Import Upstream version 0.5.4 2024-04-24 16:42:18 +08:00
tests Import Upstream version 0.5.4 2024-04-24 16:42:18 +08:00
.gitignore Import Upstream version 0.5.4 2024-04-24 16:42:18 +08:00
CHANGELOG.md Import Upstream version 0.5.4 2024-04-24 16:42:18 +08:00
COPYING Import Upstream version 0.4.15 2022-08-22 16:07:09 +08:00
README.md Import Upstream version 0.5.4 2024-04-24 16:42:18 +08:00
codecov.yml Import Upstream version 0.5.4 2024-04-24 16:42:18 +08:00
libproxy.doap Import Upstream version 0.5.4 2024-04-24 16:42:18 +08:00
meson.build Import Upstream version 0.5.4 2024-04-24 16:42:18 +08:00
meson_options.txt Import Upstream version 0.5.4 2024-04-24 16:42:18 +08:00

README.md

build codecov Coverity

Libproxy

libproxy is a library that provides automatic proxy configuration management.

The Problem

Problem statement: Applications suck at correctly and consistently supporting proxy configuration.

Proxy configuration is problematic for a number of reasons:

  • There are a variety of places to get configuration information
  • There are a variety of proxy types
  • Proxy auto-configuration (PAC) requires Javascript (which most applications don't have)
  • Automatically determining PAC location requires an implementation of the WPAD protocol

These issues make programming with support for proxies hard. Application developers only want to answer the question: Given a network resource, how do I reach it? Because this is their concern, most applications just give up and try to read the proxy from an environment variable. This is problematic because:

  • Given the increased use of mobile computing, network switching frequently occurs during the lifetime of an application
  • Each application is required to implement the (non-trivial) WPAD and PAC protocols, including a Javascript engine
  • It prevents a network administrator from locking down settings on a particular host or user
  • In most cases, the environmental variable is almost never correct by default

The Solution

libproxy exists to answer the question: Given a network resource, how do I reach it? It handles all the details, enabling you to get back to programming.

GNOME? KDE? Command line? WPAD? PAC? Network changed? It doesn't matter! Just ask libproxy what proxy to use: you get simple code and your users get correct, consistant behavior and broad infrastructure compatibility. Why use libproxy?

libproxy offers the following features:

  • support for all major platforms: Windows, Mac and Linux/UNIX
  • extremely small core footprint
  • minimal dependencies within libproxy core
  • only 4 functions in the stable-ish external API
  • dynamic adjustment to changing network topology
  • a standard way of dealing with proxy settings across all scenarios
  • a sublime sense of joy and accomplishment

Repology

Arch package Debian 12 package Fedora 37 package Fedora Rawhide package FreeBSD port Gentoo package Homebrew package Manjaro Stable package MSYS2 mingw package openSUSE Leap 15.5 package openSUSE Tumbleweed package Ubuntu 23.04 package