[SOLVED] Using "more" option in the assets endpoint seems not to be working


#1

I’m trying to be able to pick a SEO friendly image name, but the functionality doesn’t seem to be working as described in the documentation here: https://cloud.squidex.io/api/docs#operation/AssetContent_GetAssetContent

This is working:
https://url/api/assets/a6fb8e7a-3b1b-43be-8959-33759e552c7b?download=0

But this doesn’t work:

https://url/api/assets/a6fb8e7a-3b1b-43be-8959-33759e552c7b/test.jpg?download=0

I’m hosting locally through docker
I have…

  • [ ] Checked the logs and have provided uploaded a log file and provided a link because I found something suspicious there.

I’m submitting a…

  • [ x ] Regression (a behavior that stopped working in a new release)
  • [ ] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

https://url/api/assets/a6fb8e7a-3b1b-43be-8959-33759e552c7b/test.jpg?download=0 return 404

Expected behavior

https://url/api/assets/a6fb8e7a-3b1b-43be-8959-33759e552c7b/test.jpg?download=0 should return the image selected by id.

Minimal reproduction of the problem

Upload a new image, and try to use the “more” url-segment

Environment

  • [ x ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ x] Cloud version

Version: [VERSION]

Browser:

  • [ x ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge

#2

Hi,

I found the issue, there are 2 routes:

  • assets/{app}/{idOrSlug}/{*more}
  • assets/{id}/{*more}

The problem is: When you use more with the second route it matches to the first route. There is no good solution I think. Therefore just use the first route and you should be happy to go.


#3

Okay thanks :slight_smile:


#4

I will remove the more from the second endpoint.


#5