ashenchowthee / zaproxy

Automatically exported from code.google.com/p/zaproxy
0 stars 0 forks source link

Unable to save the test session via API #1607

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Start the ZAP 2.4.0
2. Save the session via API 
(http://zap/XML/core/action/newSession/?zapapiformat=XML&name=test&overwrite=tes
t)

What is the expected output? What do you see instead?
<Exception code="illegal_parameter" detail="Session path must be absolute." 
type="exception">Provided parameter has illegal or unrecognized value 
(illegal_parameter) : Session path must be absolute.</Exception>

What version of the product are you using? On what operating system?
O/S: Windows 7 Enterprise (Service Pack 1)
64 bit operating System
Zap Version: 2.4.0

Please provide any additional information below.
Unable to save the session via API.

Original issue reported on code.google.com by ganga03@gmail.com on 21 Apr 2015 at 12:28

GoogleCodeExporter commented 9 years ago
Attached screenshot.

Original comment by ganga03@gmail.com on 21 Apr 2015 at 4:59

GoogleCodeExporter commented 9 years ago
The parameter "name" should also contain be the absolute path to where the 
session should be saved (yeah, the name is not the best). For example:
C:\Directory\MySession.session

Note that the "overwrite" parameter expects a string boolean value, either 
"true" or "false".

The API used to support relative paths (or just a name) but its behaviour was 
undefined, the location where the session ended up being saved was not always 
the expected.
I guess we could allow that again but always save it to the ZAP's home 
"session" dir...

The attachment of comment #1 didn't make through.

Original comment by THC...@gmail.com on 21 Apr 2015 at 3:04

GoogleCodeExporter commented 9 years ago
I have attached screenshot again.

Original comment by ganga03@gmail.com on 27 Apr 2015 at 9:59

Attachments:

GoogleCodeExporter commented 9 years ago
ZAP has been migrated to github

This issue will be on github issues with the same ID: 
https://github.com/zaproxy/zaproxy/issues

Original comment by psii...@gmail.com on 5 Jun 2015 at 9:18