Extended Social Component - On Dispatcher/VIP | Community
Skip to main content
Shubham_borole
Community Advisor
Shubham_boroleCommunity Advisor
Community Advisor
April 6, 2017
Solved

Extended Social Component - On Dispatcher/VIP

  • April 6, 2017
  • 2 replies
  • 1880 views

Hello All,

We have extended OOTB comment component. The comments work fine on publish environments. But while on Dispatcher I see a 404 error on browser console when it tries to load the componet it see at "/services/social/getLoggedInUser.html?moderatorCheck=/content/eNet/en/path" .

We have the following  

# Allow SCF User model to check moderator rules
/6005 { /type "allow" /glob "GET /services/social/getLoggedInUser?moderatorCheck=*" }
in dispatcher ".any" file, as mentioned in  https://docs.adobe.com/docs/en/dispatcher/disp-config.html . 

Is there anything else that should be considered here?

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 JK_Kendall

From the troubleshooting section :

        A major source of problems is inserting filter rules without paying attention to the affect on earlier rules,         especially when adding a rule to deny access.

        The very first filter pattern is often used to deny everything so that following filters restore access in a         controlled manner.  When multiple filters apply to a request, the last filter that applies is the one in         effect.

And this note :

        Property Name Examples
        All property names shown, such as /0050 and /0170, should be adjusted to fit within an existing         dispatcher.any configuration file.

If you only copied one rule from the sample filters, then you need to ensure it is properly integrated into your dispatcher.any.

Any sample dispatcher configuration is only for illustrative purposes.  Dispatchers must be tuned for each deployment.  If you need more help than you're willing to show in an open forum, you could open a request for support.

- JK

2 replies

JK_Kendall
JK_KendallAccepted solution
Level 9
April 6, 2017

From the troubleshooting section :

        A major source of problems is inserting filter rules without paying attention to the affect on earlier rules,         especially when adding a rule to deny access.

        The very first filter pattern is often used to deny everything so that following filters restore access in a         controlled manner.  When multiple filters apply to a request, the last filter that applies is the one in         effect.

And this note :

        Property Name Examples
        All property names shown, such as /0050 and /0170, should be adjusted to fit within an existing         dispatcher.any configuration file.

If you only copied one rule from the sample filters, then you need to ensure it is properly integrated into your dispatcher.any.

Any sample dispatcher configuration is only for illustrative purposes.  Dispatchers must be tuned for each deployment.  If you need more help than you're willing to show in an open forum, you could open a request for support.

- JK

Shubham_borole
Community Advisor
Shubham_boroleCommunity AdvisorAuthor
Community Advisor
April 6, 2017

Thanks JK for the quick reply

    Terms & ConditionsAccessibility statement

    Loading footer...