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
We are running into Apache "uri too long" exceptions on timesheet csv urls.
The problem appears to be exacerbated since there are 5X to 10X more activity references in the url than there are actual activity choices. Should there not only be one activity reference per activity choice?
To test, I logged a time for one user for one activity. The csv had 6 activity references. I have confirmed by cutting text from the url that only the initial activity reference is necessary to run the report and obtain the expected result.
G. Boutin
The text was updated successfully, but these errors were encountered:
We are running into Apache "uri too long" exceptions on timesheet csv urls.
The problem appears to be exacerbated since there are 5X to 10X more activity references in the url than there are actual activity choices. Should there not only be one activity reference per activity choice?
To test, I logged a time for one user for one activity. The csv had 6 activity references. I have confirmed by cutting text from the url that only the initial activity reference is necessary to run the report and obtain the expected result.
G. Boutin
The text was updated successfully, but these errors were encountered: