Uses of Interface
io.envoyproxy.envoy.extensions.filters.http.admission_control.v3.AdmissionControl.SuccessCriteria.HttpCriteriaOrBuilder
Packages that use AdmissionControl.SuccessCriteria.HttpCriteriaOrBuilder
-
Uses of AdmissionControl.SuccessCriteria.HttpCriteriaOrBuilder in io.envoyproxy.envoy.extensions.filters.http.admission_control.v3
Classes in io.envoyproxy.envoy.extensions.filters.http.admission_control.v3 that implement AdmissionControl.SuccessCriteria.HttpCriteriaOrBuilderModifier and TypeClassDescriptionstatic final classProtobuf typeenvoy.extensions.filters.http.admission_control.v3.AdmissionControl.SuccessCriteria.HttpCriteriastatic final classProtobuf typeenvoy.extensions.filters.http.admission_control.v3.AdmissionControl.SuccessCriteria.HttpCriteriaMethods in io.envoyproxy.envoy.extensions.filters.http.admission_control.v3 that return AdmissionControl.SuccessCriteria.HttpCriteriaOrBuilderModifier and TypeMethodDescriptionAdmissionControl.SuccessCriteria.Builder.getHttpCriteriaOrBuilder()If HTTP criteria are unspecified, all HTTP status codes below 500 are treated as successful responses. .. note:: The default HTTP codes considered successful by the admission controller are done so due to the unlikelihood that sending fewer requests would change their behavior (for example: redirects, unauthorized access, or bad requests won't be alleviated by sending less traffic).AdmissionControl.SuccessCriteria.getHttpCriteriaOrBuilder()If HTTP criteria are unspecified, all HTTP status codes below 500 are treated as successful responses. .. note:: The default HTTP codes considered successful by the admission controller are done so due to the unlikelihood that sending fewer requests would change their behavior (for example: redirects, unauthorized access, or bad requests won't be alleviated by sending less traffic).AdmissionControl.SuccessCriteriaOrBuilder.getHttpCriteriaOrBuilder()If HTTP criteria are unspecified, all HTTP status codes below 500 are treated as successful responses. .. note:: The default HTTP codes considered successful by the admission controller are done so due to the unlikelihood that sending fewer requests would change their behavior (for example: redirects, unauthorized access, or bad requests won't be alleviated by sending less traffic).