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
I see in the logs that many people are trying to access the reports without the trailing slash, which throws a 404 error. The URL in the email notification is built with the slash, and all inner links work fine, but if one hard-types the URL, it is easy to forget the final slash. From the building perspective, the slash is important for the proper functioning of the JSON and TXT versions of the reports.
Still, maybe it would be better to enable redirect of non-slash URLs to the proper ones?
The text was updated successfully, but these errors were encountered:
Anything that helps people to not be confused is good.
On Fri, Jun 3, 2016 at 10:00 AM, Javier Otegui [email protected]
wrote:
I see in the logs that many people are trying to access the reports
without the trailing slash, which throws a 404 error. The URL in the email
notification is built with the slash, and all inner links work fine, but if
one hard-types the URL, it is easy to forget the final slash. From the
building perspective, the slash is important for the proper functioning of
the JSON and TXT versions of the reports.
Still, maybe it would be better to enable redirect of non-slash URLs to
the proper ones?
I see in the logs that many people are trying to access the reports without the trailing slash, which throws a 404 error. The URL in the email notification is built with the slash, and all inner links work fine, but if one hard-types the URL, it is easy to forget the final slash. From the building perspective, the slash is important for the proper functioning of the JSON and TXT versions of the reports.
Still, maybe it would be better to enable redirect of non-slash URLs to the proper ones?
The text was updated successfully, but these errors were encountered: