Http panels default to hex view

[GoogleCodeExporter]

The http panels default to showing data in Hex, and sometimes seem to reset to 
Hex even when manually set to Text (cant reliably reproduce this, so could be 
wrong).
Defaulting to text would be more useful.

Original issue reported on code.google.com by psii...@gmail.com on 8 Mar 2013 at 11:49

[GoogleCodeExporter]

Is that happening when changing between messages? or when restoring the 
previous selected view after ZAP starts?

Original comment by THC...@gmail.com on 8 Mar 2013 at 1:53

[GoogleCodeExporter]

Good question.
And I cant reproduce it now :(
Someone else mentioned it to me as well so its not just me ;)
Maybe its related to upgrading from a previous version?
I'll keep trying and if I cant reproduce it again I'll close the bug.

Cheers

Original comment by psii...@gmail.com on 8 Mar 2013 at 2:12

[GoogleCodeExporter]

I experienced this as well. With a clean install of 2.0.0 the first time you 
view request/response it's hex.

Original comment by kingtho...@gmail.com on 13 Mar 2013 at 12:26

[GoogleCodeExporter]

Did you delete the configurations of ZAP before installing the new version? (in 
case you had installed ZAP before).

I was able to reproduce the issue only when upgrading from a previous version.

Original comment by THC...@gmail.com on 13 Mar 2013 at 3:06

[GoogleCodeExporter]

No I hadn't deleted the config from 1.4.x.

In fact I did a side-by-side install, putting ZAP 2.0.0 in a separate directory.

I'll try renaming the directory in c:\users\<username> and see what happens.

Original comment by kingtho...@gmail.com on 19 Mar 2013 at 1:04

[GoogleCodeExporter]

ZAP, by default, uses the same directory [1] for all versions (which is where 
the configurations are saved).
As the same directory is being shared by both versions, 1.4.x and 2.0.0, each 
time you run a different version (from the previously run) the configurations 
are "updated" to the currently run version. As this issue happens after 
updating the configurations the views will default to "Hex" each time you run a 
different version.

You can workaround this issue, while running both versions, by specifying 
another directory to one of the versions using the parameter "-dir" [2] 
(simplest and fastest way is to create (or edit) a shortcut to one of ZAP 
versions and append the parameter to the "Target" field).

Let me know if this helps.

If you don't mind the question, is there a special reason to still use the 
version 1.4.x?

[1] https://code.google.com/p/zaproxy/wiki/FAQconfig
[2] https://code.google.com/p/zaproxy/wiki/FAQcmdline

Original comment by THC...@gmail.com on 26 Mar 2013 at 3:54

[GoogleCodeExporter]

Nope there isn't. I simply did a side-by-side at first to ensure I didn't run 
into any problems with 2.0.

Original comment by kingtho...@gmail.com on 28 Mar 2013 at 3:53

[GoogleCodeExporter]

From my point of view this issue can be closed. I've not experienced this issue 
on other systems which only had 2.x installed.

Original comment by kingtho...@gmail.com on 2 Jul 2013 at 3:17

[GoogleCodeExporter]

I think that it should be fixed anyway as there are some users that are still 
using old ZAP versions (<= 1.4.1) and the issue will happen once they update to 
a newer version.

Original comment by THC...@gmail.com on 2 Jul 2013 at 5:45

[GoogleCodeExporter]

Original comment by THC...@gmail.com on 2 Sep 2013 at 3:24

• Changed state: Started

[GoogleCodeExporter]

r3517

Original comment by THC...@gmail.com on 9 Sep 2013 at 2:20

• Changed state: Committed

[GoogleCodeExporter]

Confirmed this is no longer an issue in SamuraiWTF.  I was restoring an old 
copy of the config.xml with my distro cleanup scripts which was causing our 
problem.

Original comment by jus...@meeas.com on 10 Sep 2013 at 6:33

[GoogleCodeExporter]

Original comment by psii...@gmail.com on 11 Sep 2013 at 5:14

• Changed state: Fixed