Should W3C implement an all-methods, local-proxy header? Would this not solve DDoS?

[NickCarducci]

Have a new idea for web standards? Suggest it here with links to resources you'd recommend we use for follow up (technology reports, news articles, suggested contacts)
The idea is to see if these exploratory pointers spark ideas from others or suggest connections to work in progress.
Include some links here:

• nginx web app firewall vs perl config server firewall
• The use case (of this catch-all header for concurrent process requests)'s opposite (cors) to clarify (anon): Is Transmission Control Protocol of in a tamper proof (by 'tiny' explosions) device not the only way to circumvent transport correlation attacks?

Problem & Solution:

Identity Platforms on the market seem to be only partially-better than cacheing results on the server, but the local storage app seems the best for concurrent cors failures.

The impact metric benefit of an all-methods, local-proxy header prevents multiple calls no matter the different body in POST.

IF an all-methods, local-proxy header will not prevent [DDoS] by the speed of reloading the page (or running a job, and an IP address nor cookie is assumed to be available to use), would an extra package deploy a timeout somehow from the request protocol to attenuate all hacks to this card?

[RIdey1]

web standards? Suggest it here

ha jike