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

评论

Rahul k. · 评论over 1 year之前

good

Farhan S. · 评论over 1 year之前

lakshya t. · 评论over 1 year之前

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. · 评论over 1 year之前

SSM S. · 评论over 1 year之前

nice

irfanmoinuddin m. · 评论over 1 year之前

Agustina L. · 评论over 1 year之前

Rick P. · 评论over 1 year之前

Hesham M. · 评论over 1 year之前

Nas N. · 评论over 1 year之前

Gabriel D. · 评论over 1 year之前

Carlos B. · 评论over 1 year之前

Pedro S. · 评论over 1 year之前

Camilo H. · 评论over 1 year之前

Nikolaus L. · 评论over 1 year之前

Lakshhya B. · 评论over 1 year之前

Gayathri D. · 评论over 1 year之前

Luis T. · 评论over 1 year之前

Ivan G. · 评论over 1 year之前

Betty G. · 评论over 1 year之前

Valentina T. · 评论over 1 year之前

Sarthak G. · 评论over 1 year之前

Sandip C. · 评论over 1 year之前

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. · 评论over 1 year之前

Philipp M. · 评论over 1 year之前

我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。