android 能用 真是极好的！

I use this to change the content-type to text/html when viewing raw html on github. Thanks for making it.

The groups are messed if you accidently click "edit name"

有个bug，输入一个错误的URL,下载之后URL无法删除

配合卡饭上某位老兄在github上共享的规则，再也不用自己一条一条添加规格了。。。
不过要是订阅能定期自动更新，那就更好了。。。

I really like the extension and the "grouping" capabilities. However, I don't think the grouping capability is working really well for me. I will set up groups and then the groups will suddenly all disappear at some point, all the rules will still be there but the groups just disappear and all the rules will fall under "Ungrouped". Am I missing an important step?

It would be nice to be able to be able to sort the rules through drag and drop or arrow keys.

Using Firefox Developer Edition v59

---------EDIT ---03/11/2018---
I realized how to replicate the issue. After you have setup the groups, when you "Clear All History" of Firefox (I select only Cache, Cookies), the grouping gets reset.
---------EDIT ---03/11/2018---

Thanks,

Amazing! With this extension (and javascript knowledge) you can do impossible things like:
- prevent anti-hotlinking scripts from blocking or adding stuff to images on certain websites (matched by regular expressions!)
- force a sessions to not expire when you restart a browser
and much more useful stuff!

添加规则太繁琐了
能增加模板功能,或者给编辑增加个另存一条新规则吗

thuerrsch said
>Here I set up a single, simple rule to "Modify the response header", match type "All", execute type "normal", to always set the "Content-Disposition" header type to a value of "inline". That's it, two minutes to set up the whole thing, and it works beautifully!

This is also what I wanted to use this extension for, but this simple solution will remove the filename information which may be passed in that header. Instead I used the following custom function which mostly works. Note that the "tobytes" call is necessary otherwise on unicode strings firefox complains about too-high charcodes.

function tobytes (str) {
let res = "";
for (let i = 0; i < str.length; ++i) {
let code = str.charCodeAt(i);
if (code > 255) {
res += encodeURI(str[i]);
}
else {
res += str[i];
}
}
return res;
}


for (let a in val) {
if (val[a].name.toLowerCase() === 'content-disposition') {
let orig = val[a].val
console.log("orig: " + val[a].value);
let res = val[a].value.replace(/^attachment/iu, "inline");
res = tobytes(res);
console.log("res: " + res);
val[a].value = res;
}
}

Great extension !

Would it be possible to introduce a whitelist/blacklist, where you can specify on which sites should the specific rules apply, this would be also better performance wise.

Also, can you add more regex rules/matching in your wiki, for example if we want to emulate above functionality using regex:

Example rule:

- Cancel all .gif file requests to domains example.com, example1.com, example2.com

Is this the correct way to handle it, or is there a better rule/option/function in the extension ?

^http(s?)://(.*)\.example.com|example1.com|example2.com/(.*gif)

Thanks,

Kind regards

Solved my problem of being unable to open a site that needed specific headers for testing.

But I have an issue: Routes are nor being matched, but the test result successful, so the header is applied everywhere.

还不错！

it works

国内大师开发的。不错。

我新建规则，点击保存，无反应，没办法保存了。。看控制台报错是：
let dbOpenRequest = window.indexedDB.open("headereditor", 2);
一直调用的是
dbOpenRequest.onerror

This extension may look a bit frightening at first, but with some basic knowledge of http headers (and, luckily for me, no Chinese at all) it's really easy to do simple things.

The problem that Header Editor helped me to solve is as ancient as the hills: it's that infamous bug about how Firefox handles Content-Disposition: attachment headers (https://bugzilla.mozilla.org/show_bug.cgi?id=453455). A legacy extension needed replacing with Firefox Quantum. I tried a few specialized WebExtensions with little success (sometimes they worked, sometime they didn't), then I stumbled upon Header Editor.

Here I set up a single, simple rule to "Modify the response header", match type "All", execute type "normal", to always set the "Content-Disposition" header type to a value of "inline". That's it, two minutes to set up the whole thing, and it works beautifully!

Of course Header Editor can do much more complex things. With its support for custom JavaScripting it certainly has the potential to replace a whole bunch of smaller-scale extensions for all kinds of stuff related to http headers. In the right hands it can become a very powerful tool with endless possibilities. I guess that's about the best thing one can say about any piece of software.

Great.