Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redirect URL Management is not working with Delivery API #18304

Open
DanielToft opened this issue Feb 12, 2025 · 4 comments
Open

Redirect URL Management is not working with Delivery API #18304

DanielToft opened this issue Feb 12, 2025 · 4 comments
Labels

Comments

@DanielToft
Copy link

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

15.2.0

Bug summary

Redirect URL management does not work when using the Delivery API when requesting by path. The API returns a 404 instead of information about the new route.

Specifics

Database row from umbracoRedirectUrl table:
Image

Screenshot when debugging RequestRedirectService in DeliveryApi:

Image

Steps to reproduce

  • Use the Delivery Api and request by path
  • Maybe set up multiple cultures with hostnames
  • Rename a node to create the redirect
  • Request the old path

Expected result / actual result

When requesting the old path, the expected result is to receive information about the new path in the Delivery API.

Copy link

Hi there @DanielToft!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@kjac
Copy link
Contributor

kjac commented Feb 13, 2025

Hi @DanielToft,

Thanks for reaching out 😄

It sounds like this is a duplicate of #16901 - does that sound about right?

In that case, the fix is is slated for 13.7 - and 15.3, I would imagine.

@kjac kjac added the state/needs-more-info We don't have enough information to give a good reply label Feb 13, 2025
@DanielToft
Copy link
Author

Hi @kjac

It sounds a bit like the same issue, but I'm not entirely sure.

I tried changing my absolute hostnames to relative urls, but this did not fix the problem. I'm not sure what the root cause of this issue is.

Is there anything I can do to verify that this is the same issue?

@kjac
Copy link
Contributor

kjac commented Feb 13, 2025

Hiya!

Well since you're seemingly already debugging with the core source, you could try applying the code changes from #18160 to src/Umbraco.Cms.Api.Delivery/Services/RequestRedirectService.cs --- those will be forward merged to V15.3 eventually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants