You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifically:
It is my impression that requesting auth=null is intended to return all entries that have no authentication.
Instead it returns no entries, since "null" does not substring-match to "".
Thirdly, you cannot transmit the actual null object because we're restricted to strings because we're using GET requests. Fourthly, if you do in fact transmit empty-string, you get all entries in the database since the empty string is a substring of all strings. I personally can solve this with a postprocess run, but think that's definitely something that needs fixing.
I presume a similar thing would happen for the HTTPS field, but in that case you can just leave it off the query.
The text was updated successfully, but these errors were encountered:
Specifically:
It is my impression that requesting auth=null is intended to return all entries that have no authentication.
Instead it returns no entries, since "null" does not substring-match to "".
Thirdly, you cannot transmit the actual null object because we're restricted to strings because we're using GET requests.
Fourthly, if you do in fact transmit empty-string, you get all entries in the database since the empty string is a substring of all strings. I personally can solve this with a postprocess run, but think that's definitely something that needs fixing.
I presume a similar thing would happen for the HTTPS field, but in that case you can just leave it off the query.
The text was updated successfully, but these errors were encountered: