[Chilli] New Forum topic: Strange behaviour with WISPr-Redirection-URL in 1.2.9

[Ryan Day]

We'll take a look at this, thanks!

We've been testing the SVN, 1.2.9, and 1.2.8 releases over the past
couple days to try to get a comprehensive picture of the issue, I'll let
you know how 1.3 works.


Ryan

On 03/08/2012 04:14 AM, David Bird wrote:
> The issue should be fixed in:
> http://coova-chilli.s3.amazonaws.com/coova-chilli-1.3.0-svn.tar.gz
>
> .. if you can verify. There is also a new run-time option --redirurl
> which will have the WISPr-Redirection-URL put into the UAM success query
> string parameter &redirurl=... When the option is not used, chilli will
> do a HTTP redirect. 
>
>
> On Sun, 2012-03-04 at 10:17 -0500, Ryan Day wrote:
>> I'm sure this is related to the problem I've described here
>>
>>  http://lists.coova.org/pipermail/chilli/2011-November/001775.html
>>
>>
>> The patch was implemented in 1.2.9 and may be breaking functionality in
>> some situations.
>>
>> What I find amazing is that the problem described in
>> http://www.coova.org/node/5115 is exactly what I was experiencing with
>> previous versions of chilli(<1.2.9). My uamserver was being replaced by
>> my WISPr redirect and I could no longer authenticate. This patch seems
>> to work for me (me being 3 dev servers and 2 production servers).
>>
>> Any thoughts?
>>
>>
>>
>> Ryan
>>
>> On 03/04/2012 09:55 AM, David Bird wrote:
>>> Hello,
>>>
>>> The following was reported in the forum, but I will discuss it here. The
>>> issue is that chilli supports WISPr-Redirection-URL in several ways; it
>>> can be used, for example, to send users on a per session basis to
>>> alternate URLs based on the attribute not only in an Access-Accept, but
>>> also an Access-Reject. In both cases, it is sometimes desired to have
>>> the user keep going to that URL, even after their session had ended.
>>> However, obviously, that is not always the case. Possible remedies
>>> include: having an option that controls whether or not the URL value
>>> should "survive" after the session ends, making that behavior a compile
>>> time option, using a ChilliSpot-Redirect-URL VSA that can be used
>>> instead of WISPr-Redirection-URL (where the WISPr is only used in
>>> Access-Accept and only used once and the ChilliSpot-Redirect-URL VSA is
>>> the more persistent option). Any preferences or other suggestions?
>>>
>>> David
>>>
>>>
>>> On Fri, 2012-02-24 at 11:20 +0000, support at coova.com wrote:
>>>> Greetings david,
>>>>
>>>> Hello,
>>>> With the last version of coova this strange behaviour occurs when the  
>>>> WISPr-Redirection-URL is used :
>>>> - When a user is intercepted for the first time : all is ok (he performs the  
>>>> login procedure and he is redirect to the URL defined in the radius attribute  
>>>> "WISPr-Redirection-URL").
>>>> - When he comes back after logs out, coova can't intercept him (the "Move  
>>>> Temporarily" packet is wrong).
>>>> Look at the two "Move Temporarily" packet send by coova :
>>>> - First one - ok (redirect to the uamserver) :
>>>>
>>>> Read more http://www.coova.org/node/5115 -- This is an automatic message from  
>>>> Coova :: Open Source Captive Portal Access Controller and RADIUS Software To  
>>>> manage your subscriptions, browse to  
>>>> http://www.coova.org/user/1/notifications You can unsubscribe at  
>>>> http://www.coova.org/notifications/unsubscribe/sid/1?signature=7dea0a65b50949c91873109c35fa01b2
>>>>
>>> _______________________________________________
>>> Chilli mailing list
>>> Chilli at coova.org
>>> http://lists.coova.org/cgi-bin/mailman/listinfo/chilli
>>
>


-- 
Ryan Day

CirrusWorks
Beyond Convergence

750 17th Street NW, Suite 1100
Washington, DC 20006