Assest API PUT and DELETE Methods are getting 501 Not Implemented Error | Community
Skip to main content
K
kbitra1998
Level 4
March 8, 2022
Solved

Assest API PUT and DELETE Methods are getting 501 Not Implemented Error

  • March 8, 2022
  • 2 replies
  • 4216 views

Hi,

I can POST, PUT, and DELETE  in the postman using Asset  API on my localhost.

http://localhost:4502/api/assets/discounts/sitemap.xml

However, I am able to POST the asset from the postman to the Author Dev server using Asset API.  PUT and DELETE methods, on the other hand, return 501 status codes and a NOT implemented error.

 

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 kbitra1998

Hi @vijayalakshmi_s,

 

We've opened a ticket with Akamai to see if they're restricting PUT/DELETE requests. We're waiting for a response from them. I'll let you know when I get a response.


Hi @vijayalakshmi_s,

The issue has been resolved after updating the Akamai configurations and the PUT & DELETE requests are working as expected now.

Thanks for your support. Highly appreciated. 

 

2 replies

Siva_Sogalapalli
Community Advisor
Siva_SogalapalliCommunity Advisor
Community Advisor
March 8, 2022

@kbitra1998 did you configure Filter Methods in Apache Sling Referrer Filter configuration on Author Dev server where you're testing? Please compare the Filters section with your local. 

 

 

Hope this helps. 

    K
    kbitra1998Author
    Level 4
    March 9, 2022

    Hi @siva_sogalapalli 

    Thanks for the response.

    Yes, it is the same configuration as the above screenshot in my local as well as the server. 

    Somehow it is working locally but not on the server.

      Vijayalakshmi_S
      Vijayalakshmi_S
      Level 10
      March 9, 2022

      @kbitra1998 

      Can you check

      • If you have these Filter methods available in Adobe Granite CSRF Filter OSGi config as well 
      • If your Author Dev Server is behind Dispatcher,
        • check if PUT and DELETE request are allowed in filter section.
        • If yes and still not working, then enable Dispatcher Debug log and trace the request till Application server.
        tb1687196
        tb1687196
        Level 2
        March 14, 2022

        Hi @kbitra1998 ,

        In general if the Author is connected with Dispatcher and project uses CDN,  sitemap.xml also get behind it. 
        Can you confirm with any other url also if that the same behavior you are seeing. 

          K
          kbitra1998Author
          Level 4
          March 15, 2022

          Hi @tb1687196 ,

          My use case is that I want to create an asset in the dam folder using asset API, and sitemap.xml is merely name conservation. I can create the asset with a POST request, but I can't use PUT/DELETE requests to update or delete assets in the dam, even though they operate properly in my local host.

            Terms & ConditionsAccessibility statement

            Loading footer...