If you are asking what is HTTP proxy on iPhone, it is a Wi-Fi setting that sends compatible web traffic through an intermediary server before it reaches a website. On a personal iPhone, the setting belongs to one saved Wi-Fi network. It does not automatically cover cellular data, every app, or every network you join.
Choose Manual when your proxy provider gives you a server, port, username, and password. Choose Automatic when a network administrator gives you a proxy auto-configuration (PAC) URL. Leave it Off when the network does not require a proxy.
This guide explains what the setting changes, how to configure it without mixing up the fields, how to verify the route, and how to recover if the iPhone loses web access.
What Is HTTP Proxy on iPhone?
An iPhone HTTP proxy is a web-traffic relay configured for a specific Wi-Fi connection. Instead of Safari or another compatible app connecting directly to a site, it connects to the proxy. The proxy then opens or relays the connection to the destination.
The setting has three modes:
| Mode | Information required | Use it when |
|---|---|---|
| Off | Nothing | The Wi-Fi network should connect directly |
| Manual | Proxy hostname, port, and optional credentials | A provider or administrator supplied one endpoint |
| Automatic | PAC file URL | An administrator supplied rules that choose when and where to proxy |
The word HTTP describes the proxy interface, not a promise that all phone traffic is routed or that HTTPS becomes unencrypted. For a normal HTTPS site, an HTTP proxy usually relays a tunnel created with the HTTP CONNECT method. Safari still negotiates TLS with the destination inside that tunnel. The MDN guide to proxy servers and tunneling explains this distinction in more detail.

What the iPhone Wi-Fi Proxy Does—and Does Not Do
The manual setting is useful for browsing through a known egress IP, testing a website from an approved location, debugging web requests, or using a proxy required by a school or business network. It is also convenient when you want Safari traffic on one Wi-Fi network to use a proxy without installing another client.
Its scope has important limits:
- It is saved per Wi-Fi network. Join a different network and that network has its own proxy setting.
- It does not apply to cellular data. Leaving Wi-Fi normally leaves the manual Wi-Fi proxy route too.
- It is not a VPN. A VPN is designed to capture a broader set of device traffic and usually supplies an encrypted tunnel to its VPN server. See proxy server vs VPN for the routing differences.
- Apps can behave differently. Apps that honor the system web proxy may use it, while non-HTTP traffic and apps with their own networking rules may not.
- It is not the same as a managed global proxy. Organizations can deploy Apple's Global HTTP Proxy payload to supervised devices. That is an administrator-controlled configuration across networks, not the ordinary per-network Wi-Fi setting.
Apple's deployment documentation says a managed Global HTTP Proxy can use a manual server or a PAC URL. Apple also notes in its content-filtering guidance that some apps use non-HTTP connections and cannot be handled by an HTTP proxy. Those limitations are why one successful Safari test should not be treated as proof that every iPhone connection is proxied.
Before You Configure the Proxy
Collect the values from the proxy provider or network administrator first:
- Protocol: confirm that the endpoint supports HTTP proxy connections. Do not place a SOCKS5-only endpoint in this field.
- Server: a hostname such as
proxy.example.comor an IP address. - Port: a number such as
8080; use the exact port assigned to the HTTP endpoint. - Username and password: required when the endpoint uses username/password authentication.
- PAC URL: required only for Automatic mode, and normally starts with
https://. - Session or location syntax: residential gateways may encode a country, region, or sticky-session value inside the username.
Do not paste a complete proxy URL into the Server field. If you received this example:
http://username:[email protected]:8080
enter proxy.example.com as the server, 8080 as the port, and put the username and password in their separate authentication fields. Do not include http://, slashes, or credentials in the server value.
If you are unsure whether the endpoint is HTTP or SOCKS5, compare SOCKS5 vs HTTP proxy before changing the phone. The iPhone's Configure Proxy screen is for an HTTP proxy or PAC configuration; it is not a general SOCKS5 selector.
How to Configure a Manual HTTP Proxy on iPhone
Menu wording can vary slightly by iOS version, but the normal path is:
- Connect the iPhone to the Wi-Fi network that should use the proxy.
- Open Settings and tap Wi-Fi.
- Tap the information button beside the connected network.
- Scroll to HTTP Proxy and tap Configure Proxy.
- Select Manual.
- Enter the proxy hostname in Server and the numeric value in Port.
- If credentials are required, enable Authentication and enter the username and password exactly as supplied.
- Return to the previous screen so iOS retains the network setting, then test a simple HTTPS page.
Start with one known endpoint. Avoid changing the proxy, Wi-Fi network, DNS settings, and browser at the same time because that makes failures harder to isolate.
The setting may expose credentials to anyone who can unlock the phone and inspect that network. Use a unique proxy password, do not share screenshots of the fields, and remove the configuration from a borrowed or shared device when testing is complete.
How to Use Automatic Proxy Configuration
Automatic mode expects a PAC URL, not a proxy hostname. A PAC file contains JavaScript rules that return a proxy route or a direct connection for each requested URL.
To configure it:
- Go to Settings > Wi-Fi.
- Tap the information button beside the connected network.
- Tap Configure Proxy and select Automatic.
- Enter the complete PAC URL supplied by your administrator.
- Return to the network details screen and test the destinations covered by the policy.
Use the URL exactly as provided. Do not invent a PAC address from the manual proxy host, and do not paste a provider dashboard page into the URL field. If the PAC file cannot be downloaded or its rules point to an unavailable proxy, browsing can fail even though Wi-Fi remains connected.
PAC mode is most common on managed school and business networks. For a personal proxy endpoint with ordinary credentials, Manual mode is usually clearer.
How to Verify the iPhone HTTP Proxy
Test the proxy in layers so you can distinguish a routing error from a target-site error:
- With the proxy off, open
https://ipv4.unknownproxies.com/ipand note the public IPv4 address. - Enable the proxy on the current Wi-Fi network.
- Reload the IP page in a new Safari tab. The result should match the expected proxy exit rather than the original Wi-Fi address.
- Open a separate HTTPS website to confirm TLS connections work.
- Repeat the IP test in each app that you expect to use the system proxy.
- Turn off Wi-Fi briefly. If cellular data is enabled, expect its public IP to be the carrier route, not the Wi-Fi proxy.
An IP change in Safari proves that test request used the proxy. It does not prove that every app, background service, DNS query, or non-HTTP protocol follows the same path.
For a static ISP proxy or a sticky residential session, repeat the check after several requests and after reopening Safari. The exit should remain consistent for as long as the assigned session is meant to last. A rotating residential endpoint may intentionally return different exits, depending on the provider configuration.

Troubleshooting Common iPhone Proxy Problems
| Symptom | Likely cause | What to check |
|---|---|---|
| Wi-Fi connects but no pages load | Wrong server, port, or protocol | Recopy the HTTP endpoint; remove http:// and paths from Server |
| Authentication prompt repeats | Incorrect credentials or unsupported auth method | Re-enter the username/password and confirm the provider supports basic proxy authentication from iOS |
| IP address does not change | Proxy is off, wrong Wi-Fi is active, or the app bypasses it | Check Configure Proxy on the current network and retest in Safari |
| HTTP works but HTTPS fails | Tunnel or TLS inspection problem | Confirm the endpoint supports CONNECT; remove untrusted interception profiles |
| Proxy works on one Wi-Fi network only | Expected per-network scope | Configure the other saved network separately, or use a broader managed/client solution |
| Proxy stops on cellular | Expected Wi-Fi-only scope | Rejoin Wi-Fi; a manual Wi-Fi proxy does not cover mobile data |
| Business or school site fails | PAC policy, certificate, or administrator restriction | Ask the network administrator rather than changing managed profiles |
| Website returns 403 or 429 | Destination policy, permissions, reputation, or request rate | Confirm the IP first, then debug the response instead of repeatedly changing proxy fields |
Confirm the Protocol and Field Format
A hostname and port do not identify the protocol by themselves. An HTTP endpoint and a SOCKS5 endpoint begin connections differently, even if both are written as host:port. Confirm the provider's protocol and use its HTTP port.
Also check whether the username includes session controls. Removing a country or session suffix may make authentication fail or change the assigned route. Copy it as one complete username rather than trying to split it into additional iPhone fields.
Handle Captive Wi-Fi Before Enabling the Proxy
Hotels, airports, and cafes often require a sign-in page before normal internet access works. Complete that captive-portal step with the proxy off, then enable the proxy and test again. A manual proxy can prevent the portal from appearing if the network has not granted access yet.
Public Wi-Fi is also a poor place to experiment with unknown proxy services. Use HTTPS, avoid installing certificates from an untrusted proxy operator, and do not send sensitive traffic through a random free endpoint.
Treat Certificate Warnings as a Stop Signal
An HTTP proxy can relay HTTPS without decrypting it. If Safari suddenly reports an untrusted certificate after proxy setup, do not bypass the warning or install an unfamiliar root certificate just to make the page load.
TLS inspection is a separate managed capability. It should be used only in an organization you trust, with a clearly administered device and policy. For a normal commercial proxy, HTTPS destinations should retain valid certificates for their real hostnames.
Reset the Setting Safely
To remove the route, return to Settings > Wi-Fi > the network's information screen > Configure Proxy, then select Off. Test the same page again.
If direct browsing works immediately, the failure is in the proxy endpoint, authentication, PAC file, or proxy compatibility. If direct browsing still fails, troubleshoot the Wi-Fi connection itself before editing proxy settings again. Avoid resetting all network settings unless you intend to remove saved Wi-Fi, VPN, and related network configuration across the phone.
When a Proxy Is the Right Fit on iPhone
An iPhone HTTP proxy makes sense when you need a bounded web route on one Wi-Fi network—for example, permitted regional QA, checking how a public page behaves from a known IP, reproducing a proxy-specific browser issue, or using an organization-required gateway.
Choose the proxy type around the session:
- A stable ISP proxy fits repeated browser tests that should keep one exit IP.
- A sticky residential proxy can fit permitted regional tests that need a consumer-network route without changing identity mid-session.
- A rotating residential session fits independent public-page checks, not a login or multi-step account flow that expects continuity.
Use the destination within its terms and access rules. Changing the route does not grant permission, defeat account controls, or guarantee that a site accepts the request. For broader device privacy on untrusted Wi-Fi or traffic beyond web proxy support, evaluate a reputable VPN instead of assuming the HTTP proxy field covers everything.
FAQ
Should Configure Proxy be off on iPhone?
Usually yes, unless a proxy provider, employer, school, or network administrator gave you valid settings. An unexplained manual server or PAC URL can break browsing or route traffic through an operator you did not choose. Set it to Off if the network does not require it.
Does an iPhone HTTP proxy work on mobile data?
The manual setting under a Wi-Fi network does not cover cellular data. It is active only for that saved network. A managed Global HTTP Proxy or a trusted routing client is a different configuration with broader scope.
Does the iPhone support authenticated HTTP proxies?
Manual mode provides an Authentication option for a username and password. Enter the host and port separately, then copy the credentials exactly. Provider-specific IP allowlisting or unsupported authentication schemes may still require a different setup.
Can I enter a SOCKS5 proxy in the iPhone HTTP Proxy screen?
No. Do not assume iOS will detect SOCKS5 from the port. Use a compatible HTTP endpoint in the Wi-Fi setting or a trusted app that explicitly supports SOCKS5 and the traffic scope you need.
Is an HTTP proxy on iPhone safe?
It is only as trustworthy as the proxy operator and device configuration. HTTPS still protects site content when the connection is tunneled normally, but the proxy sees connection metadata and handles your route. Avoid unknown free proxies, never ignore certificate warnings, and remove settings you no longer use.
Why does Safari use the proxy but another app does not?
Safari supports the system web proxy, while another app may use a non-HTTP protocol, its own proxy setting, or networking behavior that bypasses the Wi-Fi proxy. Test every app individually and use a routing method designed for broader traffic if that is the actual requirement.
Final Thoughts
The practical answer to what is HTTP proxy on iPhone is simple: it is a per-Wi-Fi web proxy route, not a device-wide VPN. Use Manual mode for a known HTTP hostname, port, and credentials; use Automatic mode only with a real PAC URL from an administrator.
Verify the public IP in Safari, test HTTPS, and check each relevant app instead of assuming all traffic follows the route. If the phone loses web access, switch the setting Off, confirm direct Wi-Fi works, and then recheck the proxy protocol, fields, credentials, and policy one variable at a time.