Unable to get *responses* from facebook server in zap proxy
74 views
Skip to first unread message
zapp...@gmail.com
unread,
Dec 24, 2016, 10:54:38 AM12/24/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to OWASP ZAP User Group
Hello
I am not getting Server responses* from facebook in zapp proxy. I installed certificate in browser rest of all websites working fine except Facebook. Kindly help me out
Regards
zapp
kingthorin+owaspzap
unread,
Dec 24, 2016, 10:21:33 PM12/24/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to OWASP ZAP User Group
Hello
Burp suite is capturing and not getting any pinning issue? But when i try to intercept in www.facebook.com i am getting encoded response from server. ?
Why is that?
Regards
ZAhid Ali
On Sunday, December 25, 2016 at 8:21:33 AM UTC+5, kingthorin+owaspzap wrote:
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to zaprox...@googlegroups.com
Hi.
Is ZAP Root CA cert really installed and trusted? The error code
("SEC_ERROR_UNKNOWN_ISSUER") seems to indicate that it's not.
Regarding the encoded response, ZAP does not yet support that encoding.
[1] Although, in weekly releases all unsupported encodings are removed
from the request. [2]