• Resolved fullworks

    (@fullworks)


    Hi,

    I am setting up your plugin, which is fantastic by the way, but I have come across a glitch I can’t easily get to the bottom of.

    There is a certain combination ( which I haven’t fully identified when – sorry ) that results in a request string as :

    /top-level-slug/%E2%80%A6/%E2%80%A6/an-article/

    the urlencooded characters make no sense to me, and do not occur every time an-article is viewed ( so it is a combination of events that make this happen), and unfortunately breaks firewall security rules so get rejected.

    In theory there should be no reason for unprintable characters in a request string.

    Have you any ideas why / when this might happen.

    Happy to debug further, but as I can’t consistently recreate the issue I’m reaching out to you early.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author BasePress

    (@codesavory)

    Hi @fullworks,

    the url encoded characters are ellipsis which appear if an article has no KB and section selected.
    Once you have selected the Kb and section the correct URL to the article will be generated and the ellipsis will disappear.

    Thanks

    Thread Starter fullworks

    (@fullworks)

    Thanks for your fast response, that would explain why I can’t recreate it.

    It is slightly strange as the article concerned has always been attached to a KB and section.

    When I hover on a article I can see the link ( bottom of browser ) with elipses appear for about 300 m.s. and then change to a full path. (in chrome – but not in Firefox )

    I will look at changing the security rules, as it looks like this is fundamental to your design.

    • This reply was modified 5 years, 6 months ago by fullworks.
    Thread Starter fullworks

    (@fullworks)

    I have changed the rules to allow ellipses in request strings. So I will mark this resolved.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Strange characters is url trigger security rules’ is closed to new replies.