shindig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Shi" <>
Subject Re: Review Request: Ambiguous error message when gadgets are not whitelisted
Date Fri, 20 Jul 2012 00:31:59 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated July 20, 2012, 12:31 a.m.)

Review request for shindig, Ryan Baxter, Dan Dumont, and Stanton Sievers.


In Shindig when using gadget whitelisting and feature access control, there are two error

1. Gadget is not whitelisted:
403 The requested gadget is unavailable

2. Gadget is requesting features that it does not have access too
400 The requested gadget is not authorized for this container

The second error is perfect as it tells me that it has been rejected due to an authorization
error AND that it may be config related (Type 400 response).

The first error is ambiguous however, as it looks almost exactly the same as when the server
that provides the gadget.xml is unavailable and / or rejects the request. Please change (1)
to something like:
403 The requested gadget is not authorized for this container
This will tell the user that the gadget is both not authorized and via the response code (403)
that it is missing from the whitelist entirely. 

This addresses bug shindig-1818.





Marshall Shi

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message