关于“Apigee Lab 1: Generating an API Proxy Using an OpenAPI Specification”的评价

Yerson Z. · 已于 11 months前审核

Rahul k. · 已于 11 months前审核

good

Farhan S. · 已于 11 months前审核

lakshya t. · 已于 11 months前审核

I believe the lab did not explain many pain points. I ended the lab with status 404 error still I did not find anywhere explained how to resolve it. I used tools like reverse proxy but not explaination

Zacarias V. · 已于 11 months前审核

SSM S. · 已于 11 months前审核

nice

irfanmoinuddin m. · 已于 11 months前审核

Agustina L. · 已于 11 months前审核

Rick P. · 已于 11 months前审核

Hesham M. · 已于 11 months前审核

Nas N. · 已于 11 months前审核

Gabriel D. · 已于 11 months前审核

Carlos B. · 已于 11 months前审核

Pedro S. · 已于 11 months前审核

Camilo H. · 已于 12 months前审核

Nikolaus L. · 已于 12 months前审核

Lakshhya B. · 已于 12 months前审核

Gayathri D. · 已于 12 months前审核

Luis T. · 已于 12 months前审核

Ivan G. · 已于 12 months前审核

Betty G. · 已于 12 months前审核

Valentina T. · 已于 12 months前审核

Sarthak G. · 已于 12 months前审核

Sandip C. · 已于 12 months前审核

Base URL Mismatch: The OpenAPI spec specifies the base URL as https://gcp-cs-training-01-test.apigee.net/training/db, but your curl command uses https://eval.example.com/retail/v1. These base URLs need to match for the API to function correctly. Case Sensitivity: The path you are calling is /Categories, but the OpenAPI spec defines it as /categories (all lowercase). The paths in URLs are case-sensitive, so this mismatch could cause a 404 error.

Lily H. · 已于 12 months前审核