ClientWorker.js.org is still alive

[ChenYFan]

I'm very sorry that I created a new issue, but I must declare that clientworker.js.org intentionally maintains a 404 status, and it will not be removed in the future, but it was misidentified as deprecated.

clientworker is a front-end router based on serviceworker. In order to better display the 404 global hijacking and improve compatibility, the home page status of cw official documents remains 404 so that it can hit 404.html for the first time. This is one of the features and is well documented on the web. If you're accessing it with a modern browser and not a robot, it has content, and it's designed to be that way. yes

I consider this project to be a special exception and apply to the clean up bot's whitelist.

ChenYFan/ClientWorker#18

also,you can open https://clientworker.js.org through browser and curl to see different .

[MattIPv4]

👋 I'm not sure I follow why it needs to 404 initially -- can you not have an index.html that is an exact copy of 404.html, so that you serve a 200 correctly on first load?

With a 404 on first load, a lot of automation including website indexing (e.g. Google), and tools like our cleanup bot, are going to see it as not serving content.

[ChenYFan]

👋 I'm not sure I follow why it needs to 404 initially -- can you not have an index.html that is an exact copy of 404.html, so that you serve a 200 correctly on first load?

With a 404 on first load, a lot of automation including website indexing (e.g. Google), and tools like our cleanup bot, are going to see it as not serving content.

I understand what you mean, but I want to show the characteristics of cw - the ability to show content to users without the original host.

CW is diversified, and it is feasible to use non-404 intrusions-but it is extremely troublesome to modify. If the requirement of js.org is only the home page and not 404-this is ok, but it is very funny, because he can't capture other non-home paths-but in fact the home page is completely redundant, and in the end the rest of the paths still have to be processed by 404.html

The cw design is specially optimized for seo - but it is cumbersome to configure, and installation code needs to be added to each interface. If the target application is only for speeding up and displaying content, global hijacking through 404 is the easiest and cheapest way.

Of course, if js.org is unwilling to deal with it, I can add an index.html (jump to 404.html), which sounds redundant and ridiculous, but it is also the best way for both parties to solve the problem.

But in this way, the bot will not recognize that the homepage is empty, right?

[indus]

@MattIPv4 Is a whitelist feasible? I think we already had another case where we talked about it may show up in the cleanup process year after year...

[MattIPv4]

I've filed js-org/js.org-cleanup#23 to look at adding a way to have comments on entries in cnames_active.js that skip cleanup

[ChenYFan]

I've filed js-org/js.org-cleanup#23 to look at adding a way to have comments on entries in cnames_active.js that skip cleanup

Thx,i'll close this issue