关于“Apigee Lab 5: Protecting Against JSON Content Attacks”的评价

useful lab for protecting from json atack

Sungmin H. · 已于 over 3 years前审核

Eric H. · 已于 over 3 years前审核

名鴻 李. · 已于 over 3 years前审核

Satish Vithal C. · 已于 over 3 years前审核

junwoo l. · 已于 over 3 years前审核

지호 이. · 已于 over 3 years前审核

우일 박. · 已于 over 3 years前审核

상훈 박. · 已于 over 3 years前审核

Anusha T. · 已于 over 3 years前审核

Anusha T. · 已于 over 3 years前审核

Karun M. · 已于 over 3 years前审核

Oleh K. · 已于 over 3 years前审核

shahram s. · 已于 over 3 years前审核

AWESOME

Josue Raúl C. · 已于 over 3 years前审核

Jeffrey M. · 已于 over 3 years前审核

Juliana M. · 已于 over 3 years前审核

VEERLAPATI P. · 已于 over 3 years前审核

Edhy W. · 已于 over 3 years前审核

This lab just did not work - kept returning a 404 instead of invalid API key. Site was update per instructions, all started up. JSON Threat Protection policy added to createOrder. New version deployed, and shown as running. Instance shows 100% Complete. Was able to request / store a key. curl resource file created okay as per previous labs. Kept sending first curl command as indicated, but never got Invalid ApiKey - just kept returning HTTP 404 Not Found. Dropped old incognito windows / tabs, and started afresh. No change. Unable to complete the lab. There is no Support tab on the lab page, so unable to send Feedback, etc. Had to End the lab.

Ken I. · 已于 over 3 years前审核

Wisam A. · 已于 over 3 years前审核

Mbuso S. · 已于 over 3 years前审核

Farouk B. · 已于 over 3 years前审核

Andrei B. · 已于 over 3 years前审核

Stephanie M. · 已于 over 3 years前审核

Oscar Frederick P. · 已于 over 3 years前审核