You might be seeing email addresses from Raplet requests in your logs:
some HTTP servers, proxies and web frameworks log the entire URL,
including query parameters, for each incoming request. It's true that
putting the email addresses in the body of a POST request instead of
the query parameters of a GET request would stop these servers from
logging the data, but it should also be possible to configure them to
strip out the query parameters from the URL before logging. (e.g.
Rails has filter_parameters where you can specify parameters you want
to strip out.)
Unfortunately it's hard for us to use POST for Raplet requests,
because the request is originating from mail.google.com but going to
your.raplet.domain.com, so the browser will disallow it; we use JSONP
to get around the cross-domain restriction, but JSONP only supports
GET requests. One day we might use CORS
supports POST requests, instead of JSONP for Raplet requests, but that
would require Raplet authors to implement support for CORS on the
server side, and not all web frameworks support it yet.
Does that make sense?
On 13 September 2011 12:53, Tarun Pondicherry
> You received this message because you are subscribed to the Google
> Groups "Raplet developer discussion list" group.
> To post to this group, send email to raple...@googlegroups.com
> To unsubscribe from this group, send email to
> For more options, visit this group at