| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
PacProcessor relies on libpac from chromium, which is not built
for 64b right now.
Change-Id: I034932343b9aef239748511d8deb498b46e77cf2
|
| |
|
|
| |
Change-Id: Ibef01983891377b859d28cff801f48ef5d8eabb2
|
| |\
| |
| |
| |
| |
| |
| | |
should be 32 bit only."
* commit '6afcecdc15b0baec1398e344f90666e13b8e337c':
PacProcessor should be 32 bit only.
|
| | |
| |
| |
| |
| |
| | |
It depends on external/v8, which isn't ready for 64 bit yet.
Change-Id: Ibc9705665b81d3667826dedd6217f2eb6d451c81
|
| |/
|
|
| |
Change-Id: Ia1f99bd2c1105b0b0f70aa614f1f4a67b2840906
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This was found by a bug in Firefox where it expects the addresses from a
ProxySelector to be unresolved. Since ProxySelectorImpl returns unresolved
addresses the PAC version should as well to avoid breaking apps.
The ProxyServer also needed to be updated to reflect this change as it was
expecting a resolved InetSocketAddress.
Bug: 11443853
Change-Id: I3a4e9e248d22d7808603c147660df708e01cdf82
|
| |
|
|
|
|
|
|
| |
This changes the Local Proxy used in PAC to only accept connections coming
from the device.
Bug: 10230718
Change-Id: I5fbeb3aa018df5179a403301021f452e910a517d
|
| |
|
|
|
|
|
|
|
| |
This changes the PAC support to not broadcast the Proxy information until
the Local Proxy has started up and successfully bound to a port so that
the local proxy information can be guaranteed to be owned by the proxy.
Bug: 10459877
Change-Id: I175cd3388c758c55e341115e4a8241884b90d633
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This verifies both the URL and host are valid before they are passed to the
javascript for PAC. This is to protect against injection attacks.
Bug: 10230771
Change-Id: Ib1996181971a49ccd390f181ec3848124801e4d5
|
| |/
|
|
|
|
|
|
|
| |
The PAC Local Proxy priviously caught proxy broadcasts and started itself
when needed. Now it is bound by the system the same way the pac processing
service is started.
Bug: 10425091
Change-Id: I746daa21645a11aa18ef464f00c8cb5536d8c86f
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This switches the PacProcessor over to an Android Service. The service
is bound and unbound by the PacManager, which also adds it to the
ServiceManager, allowing for Context-Free access by the PacProxySelector
in all DVMs.
bug:10182711
Change-Id: Id1ff7660be56e8976cdcccd76e041feb47a17a61
|
| |/
|
|
|
|
|
| |
Changes ProxyHandler service to only be active when needed for PAC services.
Bug: 10260877
Change-Id: If42e53e805488fd08381baa96409ba3027661c70
|
|
|
PAC (Proxy auto-config) files contain a single javascript function,
FindProxyForURL(url, host). It gets called to determine what proxy should be
used for a specific request.
This adds PAC support to the system. The ProxyProperties has been modified
to hold the PAC file when one is present. The Proxy method
setHttpProxySystemProperty has been modified to insert a PacProxySelector
as the default ProxySelector when it is required. This new ProxySelector
makes calls to the ConnectivityService to parse the PAC file.
The ConnectivityService and the WifiConfigStore have been modified to support
saving the extra PAC file data.
The ConnectivityService now has a class attached (PacProxyNative) that
interfaces to the native calls for PAC files. The parsing of the PAC file
is handled by libpac (which is being added to external/) which utilizes
libv8 to parse the javascript.
As a fallback to applications that don't use the java ProxySelector, the proxy
is setup to point to a local proxy server that will handle the pac parsing.
bug:10182711
Change-Id: I5eb8df893c632fd3e1b732385cb7720ad646f401
|
