{ Community }
  • Academy
  • Docs
  • Developers
  • Resources
    • Community Articles
    • Apigee on GitHub
    • Code Samples
    • Videos & eBooks
    • Accelerator Methodology
  • Support
  • Ask a Question
  • Spaces
    • Product Announcements
    • General
    • Edge/API Management
    • Developer Portal (Drupal-based)
    • Developer Portal (Integrated)
    • API Design
    • APIM on Istio
    • Extensions
    • Business of APIs
    • Academy/Certification
    • Adapter for Envoy
    • Analytics
    • Events
    • Hybrid
    • Integration (AWS, PCF, Etc.)
    • Microgateway
    • Monetization
    • Private Cloud Deployment
    • 日本語コミュニティ
    • Insights
    • IoT Apigee Link
    • BaaS/Usergrid
    • BaaS Transition/Migration
    • Apigee-127
    • New Customers
    • Topics
    • Questions
    • Articles
    • Ideas
    • Leaderboard
    • Badges
  • Log in
  • Sign up

Get answers, ideas, and support from the Apigee Community

  • Home /
  • General /
avatar image
0
Question by Shrinivas Kulkarni · Mar 06, 2017 at 05:40 PM · 292 Views Private Cloudfault handlingraisefault4.16.09

Raise fault policy returns unexpected status code

We recently upgraded our private cloud version from 4.15.07 to 4.16.09 and are running in to an interesting situation with the RaiseFault policy. Please see the policy in question below.

In the old version when the policy executes, the status code returned is 422 as expected. However the same proxy with the policy in the new version returns a status code of 424. If I change the status code to 400, I get the response code as 400. Is there any internal mapping of status codes for certain ranges?

I also tried a similar policy implementation in public cloud and the status code is returned as expected.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<RaiseFault async="false" continueOnError="false" enabled="true" name="Validate-Query-Parameter">
    <DisplayName>Validate Query Parameter</DisplayName>
    <Properties/>
    <FaultResponse>
        <Set>
            <Headers/>
            <Payload contentType="application/json">\{"code": 422, "message": "Email address is required"}</Payload>
            <StatusCode>422</StatusCode>
            <ReasonPhrase>Email address is required.</ReasonPhrase>
        </Set>
    </FaultResponse>
    <IgnoreUnresolvedVariables>true</IgnoreUnresolvedVariables>
</RaiseFault>

raisefault-response-code.png

raisefault-response-code.png (43.2 kB)
Comment
Add comment
10 |5000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by Apigeeks only
  • Viewable by the original poster
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Close

1 Answer

  • Sort: 
avatar image
0

Answer by Dino   · Mar 06, 2017 at 06:18 PM

Yes, there's a known problem. We tracked it under ticket number APIRT-3356 .

Let me research it to see if we have a patch available for 16.09. What patch level are you using on 16.09, do you know?

@arghya das , has this fix been applied to OPDK 16.09 ?

Comment
Add comment Show 3 · Link
10 |5000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by Apigeeks only
  • Viewable by the original poster
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image Shrinivas Kulkarni · Mar 06, 2017 at 08:37 PM 0
Link

We are currently running 4.16.09.02, is the .02 the patch level of the platform?

avatar image Dino ♦♦ Shrinivas Kulkarni   · Mar 06, 2017 at 09:33 PM 0
Link

Yes. Let me check.

avatar image Shrinivas Kulkarni Dino ♦♦ · Apr 26, 2017 at 03:09 PM 0
Link

Hi Dino, were you able to confirm if a patch is available for this issue for on-prem installation?

Follow this Question

Answers Answers and Comments

40 People are following this question.

avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image

Related Questions

continueOnError="true" + RaiseFault (in shared flow): an anti pattern? 2 Answers

Fault being raised while executing a raise fault policy 3 Answers

how to get my private apigee cloud account back to active status 1 Answer

Header,Raise fault 1 Answer

How to specify additional jvm option parameters for Message Processor? 1 Answer

  • Products
    • Edge - APIs
    • Insights - Big Data
    • Plans
  • Developers
    • Overview
    • Documentation
  • Resources
    • Overview
    • Blog
    • Apigee Institute
    • Academy
    • Documentation
  • Company
    • Overview
    • Press
    • Customers
    • Partners
    • Team
    • Events
    • Careers
    • Contact Us
  • Support
    • Support Overview
    • Documentation
    • Status
    • Edge Support Portal
    • Privacy Policy
    • Terms & Conditions
© 2021 Apigee Corp. All rights reserved. - Apigee Community Terms of Use - Powered by AnswerHub
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Create an article
  • Post an idea
  • Spaces
  • Product Announcements
  • General
  • Edge/API Management
  • Developer Portal (Drupal-based)
  • Developer Portal (Integrated)
  • API Design
  • APIM on Istio
  • Extensions
  • Business of APIs
  • Academy/Certification
  • Adapter for Envoy
  • Analytics
  • Events
  • Hybrid
  • Integration (AWS, PCF, Etc.)
  • Microgateway
  • Monetization
  • Private Cloud Deployment
  • 日本語コミュニティ
  • Insights
  • IoT Apigee Link
  • BaaS/Usergrid
  • BaaS Transition/Migration
  • Apigee-127
  • New Customers
  • Explore
  • Topics
  • Questions
  • Articles
  • Ideas
  • Badges