英語 での Apigee edge の使用例とその 日本語 への翻訳
{-}
-
Colloquial
-
Ecclesiastic
-
Computer
-
Programming
Apigee Edge supports a subset of Cache-Control response header capabilities defined in the HTTP/1.1 specification.
Apigee Edge supports only a subset of Cache-Control response directives in the HTTP/1.1 specification.
Unless you are using Apigee Edge on-premise, you can't change these settings.
This defines the target URL that Apigee Edge invokes on a request to the API proxy.
Apigee Edge provides two options for deploying from the command line.
The following table describes Apigee Edge support for HTTP Cache-Control response header directives.
Here are some important HTTP status codes and what they mean in Apigee Edge.
Origin servers can include both target endpoints defined in an Apigee Edge API proxy and those created using TargetServer API calls.
Apigee Edge API Services are all about creating and consuming APIs, whether you're building API proxies as a service provider or using APIs, SDKs, and other convenience services as an app developer.
Like other Apigee Edge applications, if the proxy application is set up to listen on the secure virtual host, then it will accept incoming requests using HTTPS.
To set up a minimal API product using the Apigee Edge management API,
If the URL does not end with that domain, you cannot use your Apigee Edge credentials to log in or register on the portal.
On success, the deploy tool ZIPs up the files under/apiproxy, imports the package to your organization on Apigee Edge, and then deploys the API proxy to the'test' environment.
with Java Naming and Directory Interface(JNDI), you can make RESTful calls from JMS to backend services through Apigee Edge.
Apigee Edge supports the Cache-Control header only on responses returned from backend origin servers(the HTTP/1.1 spec allows Cache-Control headers in both client requests and origin server responses).
When an app is registered on behalf of a developer, Apigee Edge generates a"credential"(a consumer key and secret pair) that identifies the app.
Apigee Edge currently supports a subset of the HTTP/1.1 caching headers and directives(unsupported features are listed in this topic) received from backend target(origin) servers.
If Apigee Edge receives an If-Modified-Since header in a GET request, it is passed along to the origin server even if a valid cache entry exists.
Want to see Apigee Edge in action? Sign up for a free trial to design, secure, and analyze APIs that developers love.
Apigee Edge provides you with a Developer Services portal that you can use to build and launch your own customized website to provide all of these services to your development community.