[iPad] HTTPS on iPad 2 using a proxy

[DAZZD88]

Right people. Seems while testing an iPad 2 today using our wireless, we discovered that we can only enter proxy details for HTTP and not HTTPS. Have we beeen doing something wrong or are people going to suggest using a transparent proxy?

[GrumbleDook]

The proxy should be across http/https and direct (or attempt to direct) traffic across the specified port of the proxy. That is how I have it working here ... the frustration is that I can't put in some proxy exceptions as I don't want everything to go via the proxy after work have been done to trust specific sites.

[DAZZD88]

Can you elaborate a little as to what you mean by "The proxy should be across http/https and direct (or attempt to direct) traffic across the specified port of the proxy." I seem to be having a bit of a dumb moment. Lol. I was impressed with how snappy and responsive the iPad was though but I didn't like the way it's controlled (I'm used to using a HTC Desire).

[GrumbleDook]

If you stick the proxy details in, then the proxy should be used for both http and https ... I'm presently testing to make sure that this is the case for https only sites (i.e. put the proxy settings in, accessing a https only site and then checking filter logs to see if I can see that there were requests made, but can't see the content).

[FN-GM]

the frustration is that I can't put in some proxy exceptions as I don't want everything to go via the proxy after work have been done to trust specific sites.

You can if you use a .pac file. Thats what i have used in the past. Dead easy to setup.

@DAZZD88 i would use a .pac file so that you make proxy changes centrally instead of visiting each iPad. And i do 100% it works with https

[GrumbleDook]

You can if you use a .pac file. Thats what i have used in the past. Dead easy to setup.

@DAZZD88 i would use a .pac file so that you make proxy changes centrally instead of visiting each iPad. And i do 100% it works with https

.pac is not always appropriate for BYOT though ...

[DAZZD88]

Thanks @GrumbleDook that makes sense.

[FN-GM]

.pac is not always appropriate for BYOT though ...

Why not? surely it would be easier than entering them manually?

[DAZZD88]

@FN-GM I'm going to have to Google that one. So using a pac file in AD will work on an iPad? I don't understand how but then again my brain is having one of those days where things just don't sink in.

[FN-GM]

@FN-GM I'm going to have to Google that one. So using a pac file in AD will work on an iPad? I don't understand how but then again my brain is having one of those days where things just don't sink in.

You wouldnt put in in AD.

You have 2 options.

1. Deploy the .pac file by DHCP so when the iPad gets an address it will load a pac file.
2. Host the pac file on an internal webserver and point to the .pac file on each iPad.

I use option 2.

You add all your proxy settings to the file. When there is an update to this the iPads will automatically pick up the new settings.

I have a sample .pac file if you like?

[SYNACK]

.pac file is offered from a local web server and advertised to the clients via DHCP. As such it a reasonably well supported by different vendor offerings.

[DAZZD88]

Ah right. D'oh!

I think we'll pass on this. At the moment we just don't have the time to get this sorted, I know you're going to say this doesn't take long but we're too busy making up for other people's mistakes over the summer.