Page creation on AEM 6.5.5 author is giving 405 method not allowed issue | Community
Skip to main content
G
gspatil11-1
Level 2
January 29, 2021
Solved

Page creation on AEM 6.5.5 author is giving 405 method not allowed issue

  • January 29, 2021
  • 3 replies
  • 3623 views

Page creation on AEM 6.5.5 author is giving 405 method not supported issue

 

There is small pop-up message as below
 
Error
Could not create page

And over browser/developer/network tab we could see below error. Method POST not supported

Cannot serve request to /aem-perf/bin/wcmcommand in com.day.cq.wcm.core.impl.commands.WCMCommandServlet

 

<html>
<head><title>405 Method POST not supported</title></head>
<body>
<h1>Method POST not supported</h1>
<p>Cannot serve request to /aem-perf/bin/wcmcommand in com.day.cq.wcm.core.impl.commands.WCMCommandServlet</p>

<h3>Request Progress:</h3>
<pre>

 

and also aem logs are writing: 

29.01.2021 02:59:57.101 *INFO* [sling-default-3-com.mastercard.priceless.ws.eop.client.endpoint.scheduler.InventoryCacheInvalidaitonScheduler.5404] org.apache.commons.httpclient.HttpMethodDirector Retrying request
29.01.2021 03:00:00.031 *WARN* [https-jsse-nio2-10.157.248.231-25105-exec-10] com.adobe.granite.auth.cert.impl.ClientCertAuthHandler Unable to create token credentials, setting cert for uid null
com.adobe.granite.keystore.KeyStoreNotInitialisedException: Uninitialised system trust store.
at com.adobe.granite.keystore.internal.KeyStoreServiceImpl.internalGetTrustStore(KeyStoreServiceImpl.java:456)
at com.adobe.granite.keystore.internal.KeyStoreServiceImpl.getTrustStore(KeyStoreServiceImpl.java:150)
at com.adobe.granite.auth.cert.impl.ClientCertAuthHandler.findMappedUsers(ClientCertAuthHandler.java:135)
at com.adobe.granite.auth.cert.impl.ClientCertAuthHandler.extractCredentials(ClientCertAuthHandler.java:108)

 

Is there any help i could get to resolve this issue.

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

3 replies

Suraj_Kamdi
Community Advisor
Suraj_KamdiCommunity AdvisorAccepted solution
Community Advisor
January 29, 2021

@gspatil11-1 

Please refer this https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/http-405-error/td-p/261289/page/2 

    G
    gspatil11-1Author
    Level 2
    January 29, 2021
    I see Allow Empty is already checked under Apache sling referrer filter but still this issue is occuring
    G
    gspatil11-1Author
    Level 2
    February 23, 2021

    Hi All,

    We have allowed POST method for all the servlets in our tomcat server's web.xml file:  /apps_01/webapps/tomcat/conf/<tomcat_server_name>/conf/web.xml as below.                                                                                        <servlet-mapping>                                                                                                                                                                                              <http-method>POST</http-method>
    </servlet-mapping>                                                                                                                                                                                               Now 405 POST method issue is resolved and we are able to create pages over siteadmin and users/groups over useradmin on AEM. But we cannot continue with this setting on tomcat's web.xml which will get overwritten with Chef converge. Let us know if we can add the same configuration over aem war file's web.xml file. 
      G
      gspatil11-1Author
      Level 2
      March 2, 2021

      Root Cause: We have compared the tomcat configuration files between Stage and Pre-Production environment .

      The only difference we found is below request dumper filter which is enabled on STAGE but not on Pre-PROD over /apps_01/webapps/tomcat/conf/<instance_name>/conf/web.xml.

       

      <filter>

      <filter-name>requestdumper</filter-name>

      <filter-class> org.apache.catalina.filters.RequestDumperFilter                                                                                 

      </filter-class>

      </filter>

      <filter-mapping>

      <filter-name>requestdumper</filter-name>

      <url-pattern>*</url-pattern>

      </filter-mapping>                                                                                                                                     

      This configuration gets enabled when we set debug to true over environment.json file as below under SAML section. This is basically sets tomcat’s server.log in debug mode to capture SAML related requests. "SAML": { "enable": true, "debug": true,     

      Fix: I have set "debug": true, to "debug": false over environment json file and request dumper filter got removed from tomcat’s web.xml post subsequent chef converge. Now POST calls are working perfectly fine over AEM Author instance.

      Ankur_Khare
      Community Advisor
      Ankur_KhareCommunity Advisor
      Community Advisor
      February 24, 2021

      @gspatil11-1 Few questions-

      1. Is it a fresh instance

      2. If not have you made any changes to trustore or keystore try to recreate the truststore and keystore.

        Terms & ConditionsAccessibility statement

        Loading footer...