Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 16 Apr 2023 13:53:29 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 270878] www/polipo: deprecate port and schedule removal [maintainer update]
Message-ID:  <bug-270878-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270878

            Bug ID: 270878
           Summary: www/polipo: deprecate port and schedule removal
                    [maintainer update]
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: frank@harz.behrens.de

Created attachment 241527
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D241527&action=
=3Dedit
patch for port deprecation

The original software author writes on the project homepage:
"Polipo is no longer maintained

When it was first written, Polipo was probably the best HTTP proxy availabl=
e.
Since then, the web has changed, and HTTP proxies are no longer useful: most
traffic is encrypted, and a web proxy merely acts as a dumb intermediary for
encrypted traffic.

Polipo will no longer be maintained. Here are some alternatives:
* if you need your HTTP traffic to originate from a remote IP address, use a
VPN or a SOCKS5 proxy;
* if you need better caching than your browser provides, use a better brows=
er;
* if you need to share your cache between different user-agents or different
users, you're sadly out of luck;
* if you need HTTP/1.1 pipelining, you're out of luck. Much of the performa=
nce
can be recovered by using HTTP/2 or 3, but, sadly, HTTP/2 and 3 require
encryption without supporting opportunistic encryption, which makes them
difficult to deploy in many environments."

So prepare the port for removal.

--- Comment #1 from Bugzilla Automation <bugzilla@FreeBSD.org> ---
Maintainer informed via mail

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-270878-7788>