403 for long URLs | Community
Skip to main content
Manu_Mathew_
Community Advisor
Manu_Mathew_Community Advisor
Community Advisor
September 3, 2021
Solved

403 for long URLs

  • September 3, 2021
  • 1 reply
  • 1774 views

Getting 403 Forbidden for URL-- .../compare.compareonload._content_xxxxxcl_en_personal-banking_cards_credit-cards_123-dream-different-credit-card._content_xxxxxcl_en_personal-banking_cards_credit-cards_fortune-gold-card._content_xxxxxcl_en_personal-banking_cards_credit-cards_feast-gold-card.json

 

error on dispatcher error logs-as "File name too long".

How can we handle this issue.

 

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 joerghoh

The problem is the length of a filename in the dispatcher cache. Ext4 as the most common filesystem on linux imposes a limit of 255 characters on the filesystem. That means that trying to cache such files will cause a problem already (and thus cause the problem you are facing).

 

You seem to use multiple parameters as suffix, what if you separate them by a "/" (slash), so from an URL perspective it looks like a hierarchy, and you can avoid long file names.

1 reply

Raja-Karuppsamy
Community Advisor
Raja-KaruppsamyCommunity Advisor
Community Advisor
September 3, 2021

Please refer this: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/filename-too-long-error-unable-to-index-file-error-while-adding/td-p/374606

    Manu_Mathew_
    Community Advisor
    Manu_Mathew_Community AdvisorAuthor
    Community Advisor
    September 3, 2021

    This issue seems to be from the dispatcher, in publish instance there is no such issue . Seems there is some configuration to be done in dispatcher level.

    Tried few suggestions but no luck:

      joerghoh
      Adobe Employee
      joerghohAdobe EmployeeAccepted solution
      Adobe Employee
      September 3, 2021

      The problem is the length of a filename in the dispatcher cache. Ext4 as the most common filesystem on linux imposes a limit of 255 characters on the filesystem. That means that trying to cache such files will cause a problem already (and thus cause the problem you are facing).

       

      You seem to use multiple parameters as suffix, what if you separate them by a "/" (slash), so from an URL perspective it looks like a hierarchy, and you can avoid long file names.

        Terms & ConditionsAccessibility statement

        Loading footer...