Specify full URL in UAMALLOW

Hi all

We have a requirement to allow access within the walled garden to a specific URL without opening up an entire domain, eg:

www.test.com/dir1/dir2/page.html > needs to be allowed
www.test.com/anything_else > should be blocked / redirected to login page.

We've tried putting

HS_UAMALLOW=http://www.test.com/dir1/dir2/page.html

which doesn't give errors on startup, but doesn't work as expected.

How can we achieve this?
Many thanks
James.

It doesn't work that way..

It doesn't work that way.. the uamallow feature is only ip/port/protocol based, it does not inspect the url like that... Though, I suppose it could, with some processing cost/overhead. There are other options too, like privoxy or various proxy servers.

re: It doesn't work that way...

Hi David

Thanks for your reply. I would like your input on the best way to achieve what we need, either based on modifications to coova source (we have a team of developers who could probably hack around if we knew where to start looking) or in implementing a proxy-based solution.

The reason all of this came about is due to Apple's new OS 3.0 for the iPhone / iPod touch. They have introduced a 'smart' wifi login system for captive-portal based wifi hotspots which has totally broken our own hotspot solution which is based on Coova. Basically what happens is that on joining a wifi network, the iPhone tries to open

http://www.apple.com/library/test/success.html

to determine whether or not the wifi network implements a 302-style redirect. If so, it tries to be clever by asking for username/password which is then stored in the iPhone for this particular wifi network. The problem we have is that our own login pages involve javascript and other code which isn't supported through Apple's own system so people with Apple devices can't currently use our hotspots (Thanks a lot, Apple).

The solution is to allow the device to connect to the above URL (or at least 'think' it's connected) without a 302 redirect so the iPhone behaviour reverts back to pre-OS 3.0 where our users can just enter their username and password on our own web form.

At the moment we've had to add www.apple.com to our list of UAM_DOMAINs but of course this allows anyone to access all of apple.com (including the iTunes store) without paying for the wifi service.

Any more advice you can offer is greatly appreciated.

Many thanks
James.

How did you add www.apple.com to uamallowed?

You seem to provide a way to solve the MacBook/iPhone redirect problem in http://coova.org/node/2495. But I still cannot solve the problem by adding www.apple.com to uamallowed. Could you give more information?