Hi @Rohan_Garg ,  Managed to get past all but one on author instance and yes you are right, it was someone who authored a # for url which somehow internally translates to http://#. Wonder why and what causes it. Rest would need cleanup on authoring front Kindly let me know if you recognize this one....

Hi @Rohan_Garg , thank you for the response.. RTE has some weird string which will inbox you but i kind of am worried about the page path throwing WARN GET /content/cc/test/week.html HTTP/1.1] com.day.cq.rewriter.linkchecker.impl.LinkCheckerImpl Ignoring malformed URI: java.net.URISyntaxException: E...

These appear to be urls accessed and not encoded via code, some authored via RTE

Hi All, Had a question that someone might have come across and may be really easy to solve I see this on pubs and author.1. Strangely pub has the config on link checker disabled and we still see the WARNs, unsure why 2. Do we know how this can be solved and what this even means ? Limited data displa...

thanks @Saravanan_Dharmaraj ,  ended up storing it as binary under the same node 

Tried a quick poc and noticed storing as a binary property or a file with jcr data worked .. thanks all 

There is no problem with functionality but I see 2400 ish semicolon separated paths starting with /content/ . Does the 102400 include every character , I believe so .. it is not indexed and is used for sitemap ( old ways) to exclude paths that should not be exposed in the sitemap file exposed via pu...

@Rohit_Utreja @Umesh_Thakur  thank you both for your inputs..

Thank you @arunpatidar for confirming my understanding 

@arunpatidar  thanks.. when you say implement DDOS, is it blocking  IPs and domains that you speak of post monitoring?  Kindly provide an eg if you have Also, i dont believe the change to resource type will help, would it?