You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per OpenAI spec, it is standard for the model name to be included in the body of the HTTP request. Users of Inference Gateway likely want the ability to route requests based on the value of the body parameter. However, most implementations do not support routing based on request body.
It may be desirable to offer some sort of extension that populates an HTTP header with the value of the body parameter. This extension would only be called if the header has not already been populated by the client. Implementations can then route against the header (a much more common feature that is already supported natively via Gateway API).
A simple approach would be to open-source the code for the extension and publish the image along with the YAMLs required to deploy the extension in the cluster. Users can then hook up the extension using standard route extension APIs already supported by a number of implementations of Gateway API. Although there is no standard for this in Gateway API, we expect that to come soon..
The text was updated successfully, but these errors were encountered:
As per OpenAI spec, it is standard for the model name to be included in the body of the HTTP request. Users of Inference Gateway likely want the ability to route requests based on the value of the body parameter. However, most implementations do not support routing based on request body.
It may be desirable to offer some sort of extension that populates an HTTP header with the value of the body parameter. This extension would only be called if the header has not already been populated by the client. Implementations can then route against the header (a much more common feature that is already supported natively via Gateway API).
A simple approach would be to open-source the code for the extension and publish the image along with the YAMLs required to deploy the extension in the cluster. Users can then hook up the extension using standard route extension APIs already supported by a number of implementations of Gateway API. Although there is no standard for this in Gateway API, we expect that to come soon..
The text was updated successfully, but these errors were encountered: