2019-10-10 - Re: [GRASE-Hotspot] GRASEHOTSPOT with Proxy auto-config

Header Data

From: José Borges <jo***s@algardata.pt>
Message Hash: 76d8c07d352ef4dfb3bfeab6586ff5d7198d59cdd0ee49449ad10171fa87b730
Message ID: <cd350dad-484f-42be-b18d-d3a8bad4d726@grasehotspot.org>
Reply To: <CAESLx0K4p8XsuHBPs654p=Tr+uAyYSAu5CaSYrbVsmHrB+GQOA@mail.gmail.com>
UTC Datetime: 2019-10-10 02:30:08 UTC
Raw Date: Thu, 10 Oct 2019 02:30:08 -0700

Raw message 

because of the Google Chrome using/respecting HSTS and refusing to server 
http://www.google.com and serving https://www.google.com... rendering the 
browser not being redirected to captive portal, on some androids... :( 

Or for instance, on android 7.1.1 the captive portal closes if net is 
detected since it pings www.google.com/gen_204, which we cant fool android 
into thinking its not online.


On Wednesday, 9 October 2019 22:35:37 UTC+1, timwhite88 wrote:
>
> I'm not sure why you're trying to capture it. As long as you don't allow 
> it to generate the 204, then it'll work as intended. It's how Google checks 
> if it's behind a captive portal. If it doesn't get a valid connection to 
> it, then it'll assume the wifi doesn't work, or it's behind a captive 
> portal.
> The http version of it should automatically get the 302 redirect. Are you 
> seeing HTTPS requests?
>
> On Wed, 9 Oct 2019 at 19:06, José Borges <jo***.@algardata.pt 
> <javascript:>> wrote:
>
>> Hello Tim
>>
>> We are trying to capture the http(s)://www.google.com/gen_204 requests 
>> from some android devices to redirect them to the captive portal, but still 
>> havent found a good way to go about it:
>>
>> We already tried to redirect www.google.com to chilli, but that would 
>> block the search engine even after the login was made.
>>
>> Does anyone have a trick to capture the www.google.com/gen_204 and 
>> return the redirect "302" to the captive portal?
>>
>>
>>
>> On Tuesday, 8 October 2019 22:08:51 UTC+1, timwhite88 wrote:
>>>
>>> Are you trying to use it, or do you have clients using it causing 
>>> problems?
>>>
>>> There is also a second half to the story, WPAD (
>>> https://en.wikipedia.org/wiki/Web_Proxy_Auto-Discovery_Protocol). 
>>>
>>> Maybe let us know what you're trying to do. I've not seen WPAD or Proxy 
>>> auto config used in many years now, it's not normally needed except in 
>>> strange setups.
>>>
>>> Regards
>>>
>>> Tim
>>>
>>> On Mon, 7 Oct 2019 at 23:40, José Borges <jo***.@algardata.pt> wrote:
>>>
>>>> Hello
>>>>
>>>> Has anyone experience "Proxy auto-config 
>>>> <https://en.wikipedia.org/wiki/Proxy_auto-config>" with GraseHotspot?
>>>>
>>>> Would love to get your feedback on this.
>>>>
>>>> Kind regards,
>>>>
>>>> -- 
>>>> This mailing list is for the Grase Hotspot Project 
>>>> http://grasehotspot.org
>>>> --- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "Grase Hotspot" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to gr***.@grasehotspot.org.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/ffe0640c-6a3f-4c97-86b8-38c68fcbd7b6%40grasehotspot.org 
>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/ffe0640c-6a3f-4c97-86b8-38c68fcbd7b6%40grasehotspot.org?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> This mailing list is for the Grase Hotspot Project 
>> http://grasehotspot.org
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Grase Hotspot" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to gr***.@grasehotspot.org <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/3793586e-45b4-4ec0-8421-bb715c6b2fa7%40grasehotspot.org 
>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/3793586e-45b4-4ec0-8421-bb715c6b2fa7%40grasehotspot.org?utm_medium=email&utm_source=footer>
>> .
>>
>

Thread