Header Editor에 대한 리뷰
Header Editor 제작자: 泷涯, 道滿
리뷰 180개
- 5점 만점에 5점Firefox 사용자 14865188 님, 6년 전
- 5점 만점에 5점Firefox 사용자 14830170 님, 6년 전
- 5점 만점에 5점Firefox 사용자 14790139 님, 6년 전
- 5점 만점에 5점Firefox 사용자 14777917 님, 6년 전
- 5점 만점에 5점Firefox 사용자 14759223 님, 6년 전
- 5점 만점에 5점Firefox 사용자 14741090 님, 6년 전
- 5점 만점에 5점Firefox 사용자 14666101 님, 6년 전
- 5점 만점에 5점Firefox 사용자 14650562 님, 6년 전
- 5점 만점에 5점Firefox 사용자 14113497 님, 6년 전
- 5점 만점에 2점Firefox 사용자 12534656 님, 6년 전I've been very pleased with the features of this add-in, but it may have a major memory leak.
I've been using this add-in in conjunction with a script that scrapes and reloads hundreds of web pages every few minutes. I've been having memory issues with Firefox lately, so I started disabling add-ins one at a time after running it for about a week.
The moment I disabled this add-in, the process memory decreased by 18 GiB. The decrease all came from the "heap-unclassified" section of the add-ins process. This suggests that this extension (over the course of potentially millions of page loads) has somehow been allocating memory to the heap but not freeing it.
I currently have a single rule set up to modify a CORS header. Let me know if I can gather any additional information to help confirm and/or debug this issue.개발자 답글
6년 전에 게시됨Can you contact me by email? Please provide the script and rules you used. My email is sy(at)firefoxcn.net - 5점 만점에 5점Firefox 사용자 14478739 님, 6년 전
- 5점 만점에 5점Firefox 사용자 14072894 님, 7년 전It could kill HTTP Header Mangler, Redirector, url-redirector, Skip Redirect and NeatURL, but hopefully it'll have a user-friendly way to achieve what now 'custom function' feature could do; Material Design; And the authors seem to be steadfast GPL supporters.
BTW, can it delete a header?개발자 답글
6년 전에 게시됨Yes, Just set it to "_header_editor_remove_"
(BTW, in fact, I aslo like Apache License, depends on which project I am developing) - 5점 만점에 5점Firefox 사용자 14322584 님, 7년 전
- 5점 만점에 5점Firefox 사용자 14319972 님, 7년 전
- 5점 만점에 3점Firefox 사용자 11440590 님, 7년 전la extension parece muy interesante y he intentado aprender como se utiliza con diferentes tutoriales pero he llegado a la conclusion de que no me entero de nada, por lo tanto me veo obligado a preguntar si hay alguna manera de que varias direciones se puedan resolver con una unica regla en lugar de una por pagina, por ejemplo:
"https://tumangaonline.me/viewer/5b8536ef8bc73/paginated" y
"https://tumangaonline.me/viewer/5b8709870561b/paginated"
que se convertan en
"https://tumangaonline.me/viewer/5b8536ef8bc73/cascade" y
"https://tumangaonline.me/viewer/5b8709870561b/cascade"
respectivamente, vamos en definitiva que se convierta de paginated a cascade".
Estaria muy agradecido si alguien pudiese responderme.
Gracias por adelantado.
google translated
The extension seems very interesting and I have tried to learn how it is used with different tutorials but I have come to the conclusion that I do not know anything, therefore I am forced to ask if there is any way that several addresses can be solved with a only rule instead of one per page, for example:
"https://tumangaonline.me/viewer/5b8536ef8bc73/paginated" and
"https://tumangaonline.me/viewer/5b8709870561b/paginated" which become
"https://tumangaonline.me/viewer/5b8536ef8bc73/cascade" and
"https://tumangaonline.me/viewer/5b8987070561b/cascade"
respectively, let's definitively turn from paginated to cascade. "
I would be very grateful if someone could answer me.
Thanks in advance.개발자 답글
7년 전에 게시됨You can use rexexp, some examples: https://github.com/FirefoxBar/HeaderEditor/wiki/Third-party-rules , documentions: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp