Details
-
Improvement
-
Status: Closed
-
Trivial
-
Resolution: Implemented
-
Upcoming Branch
-
None
Description
Currently the demo logs, and I guess the users production logs, are cluttered up with very common and unique SetTimeZoneFromBrowser errors.
We can easily prevent that by not returning an error from SetTimeZoneFromBrowser.groovy, and so the never ending
<<Request SetTimeZoneFromBrowser caused an error with the following message: User authorization is required for this service: SetTimeZoneFromBrowser>>
from RequestHandler.java