Hello there
In the last few hours am facing issues editing workers. The page is blank and there is no way i can edit.
Is anyone facing this issue?
2 Likes
Cloudflare Status is a good category to watch 
Are you still encountering issues with this?
1 Like
I don’t know if what I am seeing is related @cloonan but…
Even after making a change (e.g. console.log("test")) in a worker, the Save and deploy button remains disabled, and the request button shows three dots.
Also, I have found that if there is no trigger enabled the URL is null
Previously (before VS Code for Web) not having an active trigger made no difference, editing a testing the worker was still possible.
Hi
As shown in the image attached, after creating the application the editing section remains blank and it’s not possible to edit.
2 Likes
Are you running any browser plug-ins/extensions @blue_new_life? Have you tried disabling them if you are to see if that makes a difference?
I do have few browsers extensions active (Deactivated all the extension, cleared cache on the browser and still the same) but I doubt that is the issue since the editing workers worked perfectly well 24h ago. I mean that those browser extensions have been active for too long and never had issues creating workers just before 24h.
Also, FYI…i use incognito.
update…
I switched browsers (firefox) and it is working now.
Here is the security headers script that i want to implement. After saving and deploying i get 404 error
export default {
async fetch(request) {
const DEFAULT_SECURITY_HEADERS = {
/*
Secure your application with Content-Security-Policy headers.
Enabling these headers will permit content from a trusted domain and all its subdomains.
@see Content-Security-Policy - HTTP | MDN
“Content-Security-Policy”: “default-src ‘self’ example.com *.example.com”,
/
/
You can also set Strict-Transport-Security headers.
These are not automatically set because your website might get added to Chrome’s HSTS preload list.
Here’s the code if you want to apply it:
“Strict-Transport-Security” : “max-age=63072000; includeSubDomains; preload”,
/
/
Permissions-Policy header provides the ability to allow or deny the use of browser features, such as opting out of FLoC - which you can use below:
“Permissions-Policy”: “interest-cohort=()”,
/
/
X-XSS-Protection header prevents a page from loading if an XSS attack is detected.
@see X-XSS-Protection - HTTP | MDN
/
“X-XSS-Protection”: “0”,
/
X-Frame-Options header prevents click-jacking attacks.
@see X-Frame-Options - HTTP | MDN
/
“X-Frame-Options”: “DENY”,
/
X-Content-Type-Options header prevents MIME-sniffing.
@see X-Content-Type-Options - HTTP | MDN
*/
“X-Content-Type-Options”: “nosniff”,
“Referrer-Policy”: “strict-origin-when-cross-origin”,
“Cross-Origin-Embedder-Policy”: ‘require-corp; report-to=“default”;’,
“Cross-Origin-Opener-Policy”: ‘same-site; report-to=“default”;’,
“Cross-Origin-Resource-Policy”: “same-site”,
};
const BLOCKED_HEADERS = [
“Public-Key-Pins”,
“X-Powered-By”,
“X-AspNet-Version”,
];
let response = await fetch(request);
let newHeaders = new Headers(response.headers);
const tlsVersion = request.cf.tlsVersion;
console.log(tlsVersion);
// This sets the headers for HTML responses:
if (
newHeaders.has("Content-Type") &&
!newHeaders.get("Content-Type").includes("text/html")
) {
return new Response(response.body, {
status: response.status,
statusText: response.statusText,
headers: newHeaders,
});
}
Object.keys(DEFAULT_SECURITY_HEADERS).map((name) => {
newHeaders.set(name, DEFAULT_SECURITY_HEADERS[name]);
});
BLOCKED_HEADERS.forEach((name) => {
newHeaders.delete(name);
});
if (tlsVersion !== "TLSv1.2" && tlsVersion !== "TLSv1.3") {
return new Response("You need to use TLS version 1.2 or higher.", {
status: 400,
});
} else {
return new Response(response.body, {
status: response.status,
statusText: response.statusText,
headers: newHeaders,
});
}
},
};
So you where using Chrome previously?
Yes! I was I was using incognito
Still not working.
I noticed that there’s 404 error requesting https://quick-edit.devprod.cloudflare.dev/undefined/zh-CN/vscode/vs/workbench/workbench.web.main/
Update…
Working on to fix the issue
目前，我的Microsoft edge浏览器依然无法显示具体代码
一样的问题, 火狐可以解决这个问题吗? 目前使用的是Chrome
Chrome 已是最新版本
版本 113.0.5672.127（正式版本） （64 位）
I also the same problem. The worker cannot open the editing interface. Don’t you developers test new features before releasing them?
the same question
It seems that after the quick editing of workers is replaced by web vscode, I can’t use the quick editing mode to edit the code of workers in chrome. Every time I open the quick editing page, the code area is blank and nothing is displayed. However, I use Safari to browse The browser can be used normally, as long as the chrome browser has this problem, can anyone help me?
There is a problem with the quick edit code in workers, entering the edit code interface has been a white screen, refresh many times or white screen, resulting in the inability to edit the code
me too，can anyone help us？
Don’t use google/incognito
It’s best to use Mozilla Firefox. Mozilla Firefox Private also works
I still can’t edit with Firefox.