Enable /bin/querybuilder on Publishing instance | Community
Skip to main content
N
nbg62
Level 4
October 24, 2022
Solved

Enable /bin/querybuilder on Publishing instance

  • October 24, 2022
  • 3 replies
  • 1775 views

hi,

 

just for a test we would like to enable querybuilder  on cloud sandbox publishing instance.

We tried changing filters.any 

Added 2 rules

 

$include "./default_filters.any"

 

/0100 { /type "allow" /path "*/bin/querybuilder*" /selectors "*" /extension "*" }

 

# allow non-public content directories if this isn't a production environment by uncommenting the next few lines
/0304 { /type "allow" /url "/apps/*" }
/0305 { /type "allow" /url "/bin/*" }

 

but no rule is allowing us to access /bin/querybuilder.json on publishing instance, we get "not found"

 

 

Thanks

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 nbg62

This is resolved by running proper pipeline (with unchecked Ignore Web Tier Configuration).

Rules that were used (I guess only 0100 would be enough)

 

/0100 { /type "allow" /url "/bin/querybuilder.json"}

/0304 { /type "allow" /url "/apps/*" }
/0305 { /type "allow" /url "/bin/*" }

3 replies

Ravi_Pampana
Community Advisor
Ravi_PampanaCommunity Advisor
Community Advisor
October 24, 2022

Hi,

 

Are you trying to access from dispatcher or publisher instance ? Try checking directly from publish instance with ip and also check whether /bin is added under below configuration

 

Apache Sling Servlet/Script Resolver and Error Handler

    N
    nbg62Author
    Level 4
    October 25, 2022

    hi,

     

    I'm trying to access on publisher instance.

    I'll check Apache Sling Servlet/Script Resolver and Error Handler

     

     

     

      Lokesh_Vajrala
      Community Advisor
      Lokesh_VajralaCommunity Advisor
      Community Advisor
      October 25, 2022

      Default dispatcher files should not be edited in Cloud Service, and default_filters.any is one of them. Instead, you can add those rules to the filters.any file and test the querybuilder in non-production instances.

       

      In case you've not noticed, there is a text block like the one below mentioned in the default filters.any file at the top of it.

      #
      # This is the default filter ACL specifying what requests are handled by the dispatcher.
      #
      # DO NOT EDIT this file, your changes will have no impact on your deployment.
      #
      # Instead modify filters.any.
      #

      But the comment mentioned in the default_filters.any for allowing /bin and /apps for non-production instances is confusing. At least, it should say, "add these rules in the filters.any file to allow non-public content directories if this isn't a production environment".

      # allow non-public content directories if this isn't a production environment by uncommenting the next few lines
      # /004 { /type "allow" /url "/apps/*"   }  # allow apps access
      # /005 { /type "allow" /url "/bin/*"    }  # allow bin path access

       

        N
        nbg62Author
        Level 4
        October 25, 2022

        Well, I stated that I updated filters.any  🙂

          N
          nbg62AuthorAccepted solution
          Level 4
          October 25, 2022

          This is resolved by running proper pipeline (with unchecked Ignore Web Tier Configuration).

          Rules that were used (I guess only 0100 would be enough)

           

          /0100 { /type "allow" /url "/bin/querybuilder.json"}

          /0304 { /type "allow" /url "/apps/*" }
          /0305 { /type "allow" /url "/bin/*" }

            Terms & ConditionsAccessibility statement

            Loading footer...