(RADIATOR) "WARNING: No such attribute" for internal use

Mark Mackay - Orcon mark at orcon.net.nz
Thu Feb 16 19:55:08 CST 2006


Hi all 
 
We're setting up proxy-radius to a customer, and want to store some
information that we lookup in a PreHandlerHook for later re-use in a
ReplyHook (to avoid a double unneeded SQL lookup, etc).
 
The current solution I've done is to do a lookup in the PreHandler and add
an attribute to the request packet:
 
    Custom-Data = XYZ
 
This doesn't get sent to the client, because Radiator comes back with log
warnings after every proxied packet: 
 
    WARNING: No such attribute Custom-Data
 
However in the ReplyHook - I can still access this information via:
 
    $originalrequest->get_attr("Custom-Data")
 
so everything works, except for the repeated warnings in the log. 
 
 
 
Maybe the solution is simply to accept and ignore these warnings - but I
can't help but think there's a better way:
 
- Is there a way to pass Variables between hooks (I've browsed the list but
they only refer to global variables, but this would be per-request variables
I guess).
 
- Is there a way to silence these warnings elegantly -- e.g. a way to strip
this attribute out from attempted transmission but keep it available from
the hooks.  
 
- Maybe a dummy dictionary entry could be used to suppress the warning but
not affect the proxy-target?
 
Regards,
Mark.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20060217/c9cb6556/attachment.html>


More information about the radiator mailing list