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

ApiError Method Not Allowed #16964

Open
benehudson opened this issue Aug 26, 2024 · 2 comments
Open

ApiError Method Not Allowed #16964

benehudson opened this issue Aug 26, 2024 · 2 comments
Assignees
Labels
state/needs-more-info We don't have enough information to give a good reply type/bug

Comments

@benehudson
Copy link

benehudson commented Aug 26, 2024

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

14.2

Note: this issue also existed on 14.1.1 and 14.1.2...I keep updating hoping it's fixed in an update.

Bug summary

When I click [Save] or [Save & Publish] on anything in the back office I get a "ApiError Method Not Allowed" error when running on my IIS Server. I do not get this error when running the site locally on my machine in IISExpress.

Specifics

This happens in every Content & Settings node. I get a red notification popup in the bottom right near the Save/Save&Pub button that says "ApiError Method Not Allowed". I have a URL rewrite setup in web.config to redirect everything from http to https. I initially thought that had something to do with it. I don't know if it matters, but this site is a Content Delivery API site. I have no view templates in this site. I was surprised to find that these errors are not logged.

Steps to reproduce

On an IIS Server attempt Save or Save & Publish any Content or Settings node.

Expected result / actual result

Expected result: save and/or save & publish

Actual result: red notification bottom-right "ApiError Method Not Allowed"

Copy link

Hi there @benehudson!

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 🤖 🙂

@Migaroez
Copy link
Contributor

Migaroez commented Nov 8, 2024

Hey @benehudson, I can't seem to reproduce this issue. Below are the steps I followed

  • Created a new umbraco project on the latest 14 (14.3.1) using the templates

  • Did an unattended install

  • Published the project trough Rider(as far as i know it uses dotnet publish) into a folder.

  • Copied the (sqllite) database into the publish folder

  • Setup an ISS site as described in the documentation https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/iis pointing towards the publish folder (no changes to the hosting model)

  • Gave the apppool permissions on the publish folder

  • Made sure default port http binding was active and no secondary site was using the binding

  • Tested the site in edge (chrome forces https redirect) => works no errors

  • Installed https://www.iis.net/downloads/microsoft/url-rewrite

  • Resarted IIS iisreset /noforce

  • Added the following to my web.config inside <system.webServer>

<rewrite>
  <rules>
    <rule name="HTTPS force" enabled="true" stopProcessing="true">
      <match url="(.*)" />
      <conditions>
        <add input="{HTTPS}" pattern="^OFF$" />
      </conditions>
      <action type="Redirect" url="https://{HTTP_HOST}{REQUEST_URI}" redirectType="Permanent" />
    </rule>
  </rules>
</rewrite>
  • Added default port https binding with ISS express dev certificate
  • Opened http://localhost/umbraco in edge => no errors
issue16964latest14.mp4

@Migaroez Migaroez added the state/needs-more-info We don't have enough information to give a good reply label Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state/needs-more-info We don't have enough information to give a good reply type/bug
Projects
None yet
Development

No branches or pull requests

2 participants