Cookie Quick Manager 的评价
Cookie Quick Manager 作者: Ysard
Ysard 的回应
开发者回应
发布于 6 年前Hi your feedback is interesting;
Nevertheless, I use this addon frequently and to my knowledge the use case you mention is functional...
However, no project is immune to a bug and you should create an issue on the project submission so that we can better understand what you are trying to do. This platform is dedicated to managing bug reports and improvement proposals while addons-mozilla.org is dedicated notations.
Basically a cookie can be refreshed/deleted by JavaScript code without reloading a page, or every time a page is viewed manually.
If you put content in the cookie that the server does not recognize as valid or that does not match the content of other cookies on the same site, or if you put information from an expired session on the server side (you can't really know that), the server may decide at any time to delete or modify your cookie.
This is totally independent of browser configuration or addon behavior.
Have you tried to visualize the status of your cookie via the Firefox development tools Ctrl+Shift+K, "Storage" tab?
You will find more information on these sites:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Session_cookies
--
https://stackoverflow.com/questions/4132095/when-does-a-cookie-with-expiration-time-at-end-of-session-expire
"This is entirely up to the user agent, i.e. the user's browser, but usually, that will indeed be when the browser is closed"
--
https://security.stackexchange.com/questions/33692/what-typically-is-the-expiration-date-of-a-session-cookie
"Cookies that 'expire at end of the session' expire unpredictably from the user's perspective!"
"If there is no expiry set on the cookie, then it is a session cookie and will live as long as the browser is open, and the sessionid is valid. If the server expires the authenticated sessions periodically, then the cookie will no longer be attached to a session on the server and will therefore be essentially null."
EDIT to reply to the Rulatir's response:
Have you thought about clicking on the button "Save the current cookie" to finalize the creation of your new cookie? I only see this explanation.
I'm just asking for a full bug report describing the situation. As it stands I can only say that this addon works because I can not reproduce your approach on various sites I tested: The addon uses the Mozilla's APIs to create the cookies and the cookie is actually created in the database AND sent by GET requests with the other cookies.
Nevertheless, I use this addon frequently and to my knowledge the use case you mention is functional...
However, no project is immune to a bug and you should create an issue on the project submission so that we can better understand what you are trying to do. This platform is dedicated to managing bug reports and improvement proposals while addons-mozilla.org is dedicated notations.
Basically a cookie can be refreshed/deleted by JavaScript code without reloading a page, or every time a page is viewed manually.
If you put content in the cookie that the server does not recognize as valid or that does not match the content of other cookies on the same site, or if you put information from an expired session on the server side (you can't really know that), the server may decide at any time to delete or modify your cookie.
This is totally independent of browser configuration or addon behavior.
Have you tried to visualize the status of your cookie via the Firefox development tools Ctrl+Shift+K, "Storage" tab?
You will find more information on these sites:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Session_cookies
--
https://stackoverflow.com/questions/4132095/when-does-a-cookie-with-expiration-time-at-end-of-session-expire
"This is entirely up to the user agent, i.e. the user's browser, but usually, that will indeed be when the browser is closed"
--
https://security.stackexchange.com/questions/33692/what-typically-is-the-expiration-date-of-a-session-cookie
"Cookies that 'expire at end of the session' expire unpredictably from the user's perspective!"
"If there is no expiry set on the cookie, then it is a session cookie and will live as long as the browser is open, and the sessionid is valid. If the server expires the authenticated sessions periodically, then the cookie will no longer be attached to a session on the server and will therefore be essentially null."
EDIT to reply to the Rulatir's response:
Have you thought about clicking on the button "Save the current cookie" to finalize the creation of your new cookie? I only see this explanation.
I'm just asking for a full bug report describing the situation. As it stands I can only say that this addon works because I can not reproduce your approach on various sites I tested: The addon uses the Mozilla's APIs to create the cookies and the cookie is actually created in the database AND sent by GET requests with the other cookies.
363 条评价
- 评分 5 / 5来自 Firefox 用户 18435690,25 天前
- 评分 5 / 5来自 Firefox 用户 18402671,1 个月前
- 评分 5 / 5来自 Edgar,2 个月前
- 评分 5 / 5来自 Pitt,3 个月前
- 评分 1 / 5来自 Craig,4 个月前
- 评分 5 / 5来自 ★ シロ ☆,4 个月前
- 评分 5 / 5来自 w27479627,5 个月前
- 评分 5 / 5来自 Firefox 用户 18239884,5 个月前
- 评分 5 / 5来自 tancrackers,6 个月前
- 评分 5 / 5来自 DELAVALLADE,6 个月前
- 评分 1 / 5来自 zer0,6 个月前
- 评分 5 / 5来自 Pamela,7 个月前
- 评分 1 / 5来自 MartyGreg,7 个月前When I click on Manage all cookies in this add-on, it shows only cookies from several sites. However when I go to FF option and look up Cookies, there are dozens of them, none shown in this manager. Unless I am doing something wrong, this is useless. I hoped this would save me several steps which I have to go through when I want to delete selected cookies thru FF Options...etc
- 评分 5 / 5来自 Firefox 用户 18134354,8 个月前
- 评分 5 / 5来自 Proto,8 个月前
- 评分 1 / 5来自 Firefox 用户 16249187,8 个月前Does not run in Firefox 117. Gives a warning that Container Tabs must be enabled, even when it is, but won't start.
- 评分 5 / 5来自 Firefox 用户 18064994,9 个月前
- 评分 5 / 5来自 Juan Lopez,9 个月前
- 评分 5 / 5来自 Mirko,10 个月前