RLS Should Log Rejections

Source: supabase/supabase#9214 · opened by @caseycrogers

Right now, there are situations where a request will be silently rejected by RLS. The client will receive a 200 with empty content and the server logs will report the same when what happened was the action was not executed because it violated an RLS rule. I understand the need to return a misleading 200 to prevent information leaks to malicious actors, but the lack of server logs makes it really hard to debug failing requests.

The server logs should log an error message when RLS rejects a request so that developers can quickly root cause a request that appears to succeed but produces no results.

See related issue:

4 years ago