janodvarko / firecookie

Automatically exported from code.google.com/p/firecookie
Other
0 stars 3 forks source link

Flag/Alert when any specific cookies are changed that are being configured for monitoring. #75

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.  This is an enhancement.
2.
3.

What is the expected output? What do you see instead?
Following steps can solve the issue:
1) Some way of configuring the cookies that needs to be monitored.
2) These cookies once set should not get modified.  If possible, we might need 
to put the feature for any specific value inside the cookie as well.
3) The users are then alerted if any such change happens.

What version of the product are you using? On what operating system?
FireBug 1.5.4  on Windows Server 2003

Please provide any additional information below.

The issue is that some cookies containing important information like Guids can 
get changed due to redirecting of the request to the wrong domain.  For e.g. QA 
domain to Prod domain.  This can result into errors that are hard to detect.  
So some way of alerting users when such kind of corruption happens would help a 
lot.

Original issue reported on code.google.com by adee...@gmail.com on 12 Oct 2010 at 1:42

GoogleCodeExporter commented 9 years ago
I like the idea. Any tips how to UI should looks like? Perhaps cookie 
breakpoints could be somehow utilized...?

Honza

Original comment by odva...@gmail.com on 19 Oct 2010 at 9:16

GoogleCodeExporter commented 9 years ago
Thanks Honza for the positive comments.  

For the UI, I am thinking there can be another option under cookies section for 
configuring rules for monitoring the cookies.  It can take following 
information:

    Name:RuleOption:TimeStamp:IgnoreString:Status:
                - Name: name of cookie or cookielet
                - RuleOption: value [CHANGE|NOCHANGE] - option to tell how should the cookies behave
                - TimeStamp: value [8|0] - 8 means cookie has timestamp and should be ignored; 0 means cookie does not have timestamp
                - IgnoreString: value [BLANK|%3B|...] - BLANK means no string to ignore, %3B means string to be ignored within a cookie or cookielet's value
          o Example:
          o cookie_abc:NOCHANGE:8::
          o cookie_2=:NOCHANGE:0::

    Then some button (Cookie button) may turn red indicating that the rule has been triggered.  On click of the button, it can show the errors and change in values.

Thanks.
Cheers,
Adee

Original comment by adee...@gmail.com on 20 Oct 2010 at 1:57

GoogleCodeExporter commented 9 years ago
It sounds like this issue is all about recognizing cookie changes.
So "Break On Cookie Change" covers the JavaScript changes and the rest should 
be covered by checking the option "Show Logs in Console".

Adee, is that enough for you?

Please note that Firecookie is integrated into Firebug since version 1.10a11.

Sebastian

Original comment by sebastia...@gmail.com on 25 Jun 2012 at 12:01

GoogleCodeExporter commented 9 years ago
Moved to: Issue fbug:5611

Original comment by sebastia...@gmail.com on 25 Jun 2012 at 12:01