Invalid URL Redirection and 404 Error
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Quote from bulli on February 25, 2025, 17:45Dear Support Team,
We have noticed that the URL /shop/page/3 works correctly. However, a URL with the following format is being stored in the database:
/shop/page/6/window.location.href/page/3/i/page/2/i/3/8/i/8This URL redirects to our homepage and results in a 404 error. We discovered this issue with the help of WP Rocket.
Could you please assist us in identifying the cause of this problem? Could it possibly be related to the Husky filters or another part of the system?
Additionally, we would like to know if this URL is being generated by you or if it is caused by WP Rocket or another plugin.
WP Rocket provided the following feedback:
"If they are legit pages, and you want WP Rocket to optimize them, then it's perfect. However, I found this URL that doesn't work:
/shop/page/6/window.location.href/page/3/i/page/2/i/3/8/i/8This URL redirects to the homepage (Error 404). The regular paginated URLs like /shop/page/3 work normally, but I'm wondering about those URLs with /window.location.href/ in them.
As I see it, those may not be valid URLs, and we should stop trying to optimize them. Maybe the query strings belong under cache for query strings like:
=lander_stadte,product_cat?."Could it be that this URL is the result of faulty caching or incorrect URL generation? We would greatly appreciate your assistance in resolving this issue.
Best regards
Dear Support Team,
We have noticed that the URL /shop/page/3 works correctly. However, a URL with the following format is being stored in the database:
/shop/page/6/window.location.href/page/3/i/page/2/i/3/8/i/8
This URL redirects to our homepage and results in a 404 error. We discovered this issue with the help of WP Rocket.
Could you please assist us in identifying the cause of this problem? Could it possibly be related to the Husky filters or another part of the system?
Additionally, we would like to know if this URL is being generated by you or if it is caused by WP Rocket or another plugin.
WP Rocket provided the following feedback:
"If they are legit pages, and you want WP Rocket to optimize them, then it's perfect. However, I found this URL that doesn't work:
/shop/page/6/window.location.href/page/3/i/page/2/i/3/8/i/8
This URL redirects to the homepage (Error 404). The regular paginated URLs like /shop/page/3 work normally, but I'm wondering about those URLs with /window.location.href/ in them.
As I see it, those may not be valid URLs, and we should stop trying to optimize them. Maybe the query strings belong under cache for query strings like: =lander_stadte, product_cat?."
Could it be that this URL is the result of faulty caching or incorrect URL generation? We would greatly appreciate your assistance in resolving this issue.
Best regards
Quote from Pablo Borysenco on February 26, 2025, 10:26Hello
Unfortunately I don't know what third-party plugin can cause such behavior. Our plugin can't generate such URLs, much less write them to the database.
Hello
Unfortunately I don't know what third-party plugin can cause such behavior. Our plugin can't generate such URLs, much less write them to the database.
Quote from bulli on February 26, 2025, 16:44Great, thank you, you've already helped me. Will test it.
Best regards
Great, thank you, you've already helped me. Will test it.
Best regards
Quote from bulli on March 20, 2025, 19:50Hello Husky Filter Team,
We recently contacted you regarding an issue where URLs containing
window.location.hrefare being automatically generated and stored in our database.URL***/window.location.href/page/6/window.location.href/page/3/i/i/page/2/i/9/10/10/3/window.location.href/2/2/10/3
In a previous discussion on your support forum, you mentioned that Husky Filter does not generate such URLs or store them in the database. However, we are still encountering this issue.
Additional Details:
- We are using Husky Filter along with WCFM Marketplace.
- The issue was initially detected through WP Rocket, which highlighted invalid URLs being stored and attempted to optimize them.
- The affected URLs seem to be dynamically created and indexed by bots like GPTBot and others.
- The entries appear to be stored in the database table
wcfm_detailed_analysis.Questions:
- While Husky Filter does not generate these URLs, could it still be indirectly involved due to filter behavior?
- Do you have any insights on whether Husky Filter interacts with WCFM or another plugin in a way that could result in such URL patterns?
- Could improper caching or query string manipulation be causing this issue?
- Do you have any recommendations on how to prevent these types of URLs from being generated?
We appreciate your help in troubleshooting this issue!
Best regards,
Hello Husky Filter Team,
We recently contacted you regarding an issue where URLs containing window.location.href are being automatically generated and stored in our database.
URL***/window.location.href/page/6/window.location.href/page/3/i/i/page/2/i/9/10/10/3/window.location.href/2/2/10/3
In a previous discussion on your support forum, you mentioned that Husky Filter does not generate such URLs or store them in the database. However, we are still encountering this issue.
Additional Details:
- We are using Husky Filter along with WCFM Marketplace.
- The issue was initially detected through WP Rocket, which highlighted invalid URLs being stored and attempted to optimize them.
- The affected URLs seem to be dynamically created and indexed by bots like GPTBot and others.
- The entries appear to be stored in the database table
wcfm_detailed_analysis.
Questions:
- While Husky Filter does not generate these URLs, could it still be indirectly involved due to filter behavior?
- Do you have any insights on whether Husky Filter interacts with WCFM or another plugin in a way that could result in such URL patterns?
- Could improper caching or query string manipulation be causing this issue?
- Do you have any recommendations on how to prevent these types of URLs from being generated?
We appreciate your help in troubleshooting this issue!
Best regards,
Quote from Pablo Borysenco on March 21, 2025, 11:40Hello
Unfortunately I have no ideas.
All I can suggest is to change the SEO URL setting (enable or disable). This option changes the URL generation and you can check if the error has changed.
Hello
Unfortunately I have no ideas.
All I can suggest is to change the SEO URL setting (enable or disable). This option changes the URL generation and you can check if the error has changed.
Quote from bulli on March 21, 2025, 18:57Hello, thanks for the support. I'll give it a try.
Hello, thanks for the support. I'll give it a try.