Assets HTTP MOVE API giving 405 response | Community
Skip to main content
R
RahulMohan
Level 3
October 30, 2024
Solved

Assets HTTP MOVE API giving 405 response

  • October 30, 2024
  • 3 replies
  • 837 views

Hi, I'm trying to move some assets using the HTTP MOVE API. But I'm getting 405 response saying Method not allowed. It was working till last week. Any idea how to fix this?

Thanks,
Rahul

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by EstebanBustamante

Hi,

 

There are two reasons why this could happen:

  1. You are not using the correct HTTP method when invoking the API. Check your code is using the correct method while invoking the API

  2. The server is blocking (not allowing) the HTTP method. This could be denied at the dispatcher level or at the publisher level as well. The best way to check is to hit the publisher directly. If it works, it means your dispatcher has been updated and you are no longer allowed to use the HTTP method on your server.

Hope this helps.

3 replies

abhishekanand_
Community Advisor
abhishekanand_Community Advisor
Community Advisor
October 30, 2024

Hi @rahulmohan 

 

Ensure that the user or service account making the HTTP MOVE request has adequate permissions, If AEM is accessed through a dispatcher, confirm that the dispatcher allows HTTP MOVE methods. Dispatcher configurations sometimes block specific methods for security reasons, and updates may inadvertently reset or restrict them review any recent updates to AEM, dispatcher, or network configurations.

Abhishek Anand
    EstebanBustamante
    Community Advisor and Adobe Champion
    EstebanBustamanteCommunity Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    November 4, 2024

    Hi,

     

    There are two reasons why this could happen:

    1. You are not using the correct HTTP method when invoking the API. Check your code is using the correct method while invoking the API

    2. The server is blocking (not allowing) the HTTP method. This could be denied at the dispatcher level or at the publisher level as well. The best way to check is to hit the publisher directly. If it works, it means your dispatcher has been updated and you are no longer allowed to use the HTTP method on your server.

    Hope this helps.

    Esteban Bustamante
      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      November 5, 2024

      @rahulmohan Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...