[publishfarm/-] [actionblocked] | Community
Skip to main content
Sean-McK
Sean-McK
Level 4
November 17, 2021
Solved

[publishfarm/-] [actionblocked]

  • November 17, 2021
  • 2 replies
  • 5838 views

hey all......quick question. I am running AEM as cloud service and have the default dispatcher setup for venia, and when I request a product details page I get the following
"GET /products/product-page.html/carina-cardigan.html" -0ms [publishfarm/-] [actionblocked] publish-?????????????.adobeaemcloud.com
seems like the publish farm is just denying it, but I can't find the issue. I am using aem-cif-guides-venia as my compare. Any help?

    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 Sean-McK

    I found out this is a bunch of issues for me. I have updated dispatchers as well as sling mappings and it is working now.

    2 replies

    Raja-Karuppsamy
    Community Advisor
    Raja-KaruppsamyCommunity Advisor
    Community Advisor
    November 17, 2021

    @sean-mck 

    ** Can you please let us know how are you accessing the product page ? with HTTP or HTTPS ?

    ** Can you change the dispatcher log level to DEBUG and access the site page & share the complete log, so that we can conclude whether publish farm is denying/blocking your request ?

    ** What is the error page or response you are getting while accessing the product page ?

     

      Sean-McK
      Sean-McKAuthorAccepted solution
      Level 4
      November 17, 2021

      I found out this is a bunch of issues for me. I have updated dispatchers as well as sling mappings and it is working now.

        S
        SeanMc5
        March 19, 2024

        @seanmc5 It seems that existing URL based format allow is not working. i.e.

         

        /0112 { /type "allow" /url "* *.webp *"  }  # enable webp

        The above code is not working. The below code is working in AEM as a Cloud Service

         

        /0138 { /type "allow" /method "GET" /extension '(css|eot|gif|ico|jpeg|jpg|js|gif|png|webp|svg|swf|ttf|woff|woff2)' }

        Thanks for your quick reply.

         

         


        /0112 { /type "allow" /url "* *.webp *"  }  # enable webp

        that wouldn't work because of the regular expression i believe 

         

        /0112 { /type "allow" /url "*/*.webp"  }  # enable webp

        I think that would work, but doing it by url is not great, but by extension is best. that is how you handle special extensions....newer version of AEM accounts for webp

         

         

        S
        salonis29384287
        New Member
        August 22, 2023

        Can You Provide a Specific Solution It will be really helpful to us 

        Terms & ConditionsAccessibility statement

        Loading footer...