Describe the bug
When I visit a browse by page (eg. https://demo.dspace.org/browse/dateissued?bbm.page=1&startsWith=2023) and open the developer tools, I see multiple requests that result in 401 responses. I assume they are related to features only an admin should be able to access. These requests should not be made, there should be a check in place that only authorized users fire these requests.
Failing requests were observed on these paths:
/server/api/system/scripts/metadata-import
/server/api/system/scripts/metadata-export
The bug is present in both DSpace 9.3. and 10.
To Reproduce
Steps to reproduce the behavior:
- Open https://demo.dspace.org/browse/dateissued?bbm.page=1&startsWith=2023 as an anonymous user
- Open the dev tools and the console or network tab and observe the failed requests
Note: This does not happen everytime, likely because of a race condition with observables in the frontend code. Just try it out several times.
Expected behavior
When visiting browse-by pages as an anonymous user, I don't encounter 401 errors/responses.
Related work
Similar to #5931, fix is here: #5932
Describe the bug
When I visit a browse by page (eg. https://demo.dspace.org/browse/dateissued?bbm.page=1&startsWith=2023) and open the developer tools, I see multiple requests that result in 401 responses. I assume they are related to features only an admin should be able to access. These requests should not be made, there should be a check in place that only authorized users fire these requests.
Failing requests were observed on these paths:
/server/api/system/scripts/metadata-import
/server/api/system/scripts/metadata-export
The bug is present in both DSpace 9.3. and 10.
To Reproduce
Steps to reproduce the behavior:
Note: This does not happen everytime, likely because of a race condition with observables in the frontend code. Just try it out several times.
Expected behavior
When visiting browse-by pages as an anonymous user, I don't encounter 401 errors/responses.
Related work
Similar to #5931, fix is here: #5932