This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.
Log in to ask a question

Apigee X support for HTTP/1.0

Posted on 08-19-2024 09:57 AM
RTeja
Bronze 2
Bronze 2
Reply posted on --/--/---- --:-- AM

We have a legacy application which is trying to invoke apigee proxy using http/1.0 protocol. Their transaction fails with a HTTP 426 response code. I would like to know if HTTP/1.0 is not supported in ApigeeX.

1 2 308
Topic Labels
2 REPLIES 2

Posted on --/--/---- --:-- AM
dchiesa1
Staff
Reply posted on --/--/---- --:-- AM

I would like to know if HTTP/1.0 is not supported in ApigeeX.

Short answer: No.

Apigee X runs in Google Cloud, and when an external client or app connects into Apigee X - in other words, when an external client sends in an API request that gets managed by Apigee X - that request goes through the Google Cloud External Load Balancer (sometimes abbreviated as XLB).

The thing that is sending back the 426 status code, "upgrade required", is the Google Cloud External Load Balancer. This is a general-purpose networking service, a part of Google Cloud that you "just get" when you use Apigee X. It's called a "load balancer", but really it is a front end networking service that routes inbound calls to something upstream - like a microservice, or a website, or etc. It can be used independently of Apigee X; for example if you have a website that you load into Cloud Run, then requests originating from external web browsers will go through the Google Cloud External Load Balancer to reach that website. So that's what I mean by "general purpose" networking service. But in the Apigee X scenario, it's the front-door to your Apigee X system.

The External Load Balancer supports HTTP 1.1 or HTTP 2. (see the relevant documentation)

XLB-http.png

A client cannot use HTTP 1.0 to communicate through the XLB. Hence you cannot use HTTP 1.0 to reach APIs managed within Apigee X.

Posted on --/--/---- --:-- AM
waciii-rtp-nc
Bronze 2
Bronze 2
In response to dchiesa1
Reply posted on --/--/---- --:-- AM

Has this answer changed for either Apigee X or Hybrid?  I'm seeing results that don't comport with what I've been told which was basically: "Client cannot use HTTP/1.0 with either Apigee X or Apigee Hybrid"

We have Apigee X and Apigee Hybrid:

Clients (HTTP/1.0) switching from Apigee X (where this works fine) to Apigee Hybrid 1.13.1 (AWS) see 426 Upgrade Required

We upgraded to Apigee Hybrid 1.14.1 and Clients (HTTP/1.0) no longer see 426 Upgrade Required.  When we hit the now dark (yet to be deleted) 1.13 Clusters, we get 426 Upgrade required

Support has said this should NOT work and yet I'm seeing it work with both X and Hybrid 1.14

0 Likes
Top Solution Authors
View all