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
Currently, reading json files seems to go through the web server when they could (and, IMO, should) be requested from the disk. Forcing them to come from the web server means that files such as serviceCreds.json can be read by anyone.
The text was updated successfully, but these errors were encountered:
We are discussing moving all sensitive data out of the documentRoot or
possibly making it private with a .htaccess file. Thank you for bringing
this to our attention
On Wed, Jun 25, 2014 at 12:27 AM, Ben Boeckel [email protected]
wrote:
Currently, reading json files seems to go through the web server when they
could (and, IMO, should) be requested from the disk. Forcing them to come
from the web server means that files such as serviceCreds.json can be
read by anyone.
—
Reply to this email directly or view it on GitHub #2.
Currently, reading json files seems to go through the web server when they could (and, IMO, should) be requested from the disk. Forcing them to come from the web server means that files such as
serviceCreds.json
can be read by anyone.The text was updated successfully, but these errors were encountered: