You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
On one website I use your lib on, they have a framework that encapsulate links using 'clkn' href.
As a consequence:
when on our website a users clicks on a button, it works fine
when the lib crawls the link, it doesn't interpret the href (but just read it and check the litteral link it would be), find its 410 -> test is red.
So ok for the user, but red for the crawler. As it works for the end user, I'd like the crawler to check the actual redirected url, and return whether this end-url is ok or not.
Describe the solution you'd like
When an href is shaped as : href = clkn/http(s)/www.google.com/"
Then the tested url should be : http(s)://www.google.com/
And the test should be red or green based on this url (and not http(s)://clkn/http(s)/www.google.com/*)
Describe alternatives you've considered
Being able to ignore such pattern is a good temporary option. But any way to handle it would be nice.
This is not an HTML standard, so support for it will likely never make it into the core of this project. It will be possible as a plugin in the future when that architecture has been put in place. Another possible idea is to add some kind of a "filter" event to the API for customizing the link filter.
Is your feature request related to a problem? Please describe.
On one website I use your lib on, they have a framework that encapsulate links using 'clkn' href.
As a consequence:
So ok for the user, but red for the crawler. As it works for the end user, I'd like the crawler to check the actual redirected url, and return whether this end-url is ok or not.
Describe the solution you'd like
When an href is shaped as : href = clkn/http(s)/www.google.com/"
Then the tested url should be : http(s)://www.google.com/
And the test should be red or green based on this url (and not http(s)://clkn/http(s)/www.google.com/*)
Describe alternatives you've considered
Being able to ignore such pattern is a good temporary option. But any way to handle it would be nice.
Additional context
The documentation about clkn redirect
https://documentation.unbounce.com/hc/en-us/articles/360038828772-Why-Are-Links-on-My-Landing-Page-Wrapped-in-clkn-clkg-
The text was updated successfully, but these errors were encountered: