issues with REST endpoint

[Joshua Kim]

Hello,

We used DSpace 9.2. In the dspace.log file, I have found many errors with REST endpoint. For example, 

1. The response for 'https://xxxxxxxxx/server/api/core/items/eba1c085-fddc-4de9-bb30-8b17c2012d1d/bundles?size=9999' has the self link 'https://xxxxxxxxxxx/server/api/core/items/eba1c085-fddc-4de9-bb30-8b17c2012d1d/bundles?embed=primaryBitstream&size=1000'. These don't match. This could mean there's an issue with the REST endpoint

2. The response for 'https://xxxxxxxx/server/api/core/bundles/9d18168a-c708-494f-81ac-920a0c802378/bitstreams?page=0&size=5' has the self link 'https://xxxxxxx/server/api/core/bundles/9d18168a-c708-494f-81ac-920a0c802378/bitstreams?page=0&embed=accessStatus&size=5'. These don't match. This could mean there's an issue with the REST endpoint
 issue with the REST endpoint

Is this a normal process in DSpace? Or is there anything I can do to fix this issue?

Thank you in advance.

[DSpace Technical Support]

Hello,

These logs of "The response for X has the self link Y" are developer warnings that are harmless and often can be ignored.  They do occur for most sites, especially on item pages and there is an open ticket to eventually clean these up:  https://github.com/DSpace/DSpace/issues/8577

Occasionally though, lots of these can be a sign of something else going on - are you seeing any additional error messages or buggy behavior on the UI pages where the warnings were triggered? If not, these logs can be safely ignored. 

Best,

-Lia

[Milan Majchrak]

Hello,

We also encountered these console warnings and addressed them in this PR:
https://github.com/DSpace/dspace-angular/pull/6083

Feel free to take a look at the solution, review it, and test it on your side. We are already running this fix in production.

From +dataquest,
Milan Majchrak