{ 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
    • 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 /
  • Edge/API Management /
avatar image
0
Question by Sanjay Kammili · Jan 26, 2016 at 10:42 PM · 1.6k Views proxy configurationhttpproperty

Proxy Endpoint HTTP allow method properties not working

I have following proxy endpoint properties set

<HTTPProxyConnection>

<BasePath>/v1/data</BasePath>

<Properties>

<Property name="allow.http.method.GET">true</Property>

<Property name="allow.http.method.POST">false</Property>

<Property name="allow.http.method.PUT">false</Property>

<Property name="allow.http.method.DELETE">false</Property>

<Property name="allow.http.method.HEAD">false</Property>

<Property name="allow.http.method.OPTIONS">false</Property>

<Property name="allow.http.method.TRACE">false</Property>

<Property name="allow.http.method.PATCH">false</Property>

</Properties>

<VirtualHost>default</VirtualHost>

</HTTPProxyConnection>

But no luck, its allowing all methods. I see in trace session that these properties are there, so it is deployed.

Thanks, Sanjay

Comment
Add comment Show 1
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 Anil Sagar @ Google ♦♦   · Jan 27, 2016 at 04:12 AM 0
Link

Dear @skammili , Welcome to Apigee Community :) Thank you for highlighting same. I can able to reproduce same, clearly it looks like a bug. We will get back to you and keep you updated.

Close

2 Answers

  • Sort: 
avatar image
5
Best Answer

Answer by Omid Tahouri   · Jan 26, 2016 at 10:52 PM

I've not had the time to verify the behaviour of setting those properties, but there may be an alternative solution for what you're trying to achieve...

What about raising a fault based on the request method? You could do this as the first step.

<PreFlow name="PreFlow">
        <Request>
            <Step>
                <Condition>request.verb != "GET"</Condition>
                <Name>fault-method-not-allowed</Name>
            </Step>
	...

Where "method-not-allowed-fault" is a RaiseFault policy that could look like this:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<RaiseFault enabled="true" continueOnError="false" async="false" name="fault-method-not-allowed">
	<DisplayName>fault-method-not-allowed</DisplayName>
	<FaultResponse>
		<Set>
			<StatusCode>405</StatusCode>
			<Headers>
				<Header name="Allow">GET</Header>
			</Headers>
		</Set>
	</FaultResponse>    
	<IgnoreUnresolvedVariables>true</IgnoreUnresolvedVariables>
</RaiseFault>

Comment
Add comment Show 1 · 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 Sanjay Kammili · Jan 27, 2016 at 05:41 PM 0
Link

Thank you Omid for the aleternate solution.

avatar image
4
Best Answer

Answer by tskumar@apigee.com · Jan 27, 2016 at 12:00 PM

HTTP properties "allow.http.method.<VERB>" is not supported in the recent releases. We have to handle through "RaiseFault" policy in the message flow, as suggested by Omid.

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 Anil Sagar @ Google ♦♦   · Jan 27, 2016 at 12:16 PM 0
Link

@docs , We need to update documentation & remove the references. Thank you :)

avatar image jonesfloyd ♦♦ Anil Sagar @ Google ♦♦ · Jan 27, 2016 at 03:05 PM 0
Link

Removed from the docs. Thanks for the info.

avatar image Anil Sagar @ Google ♦♦ jonesfloyd ♦♦   · Jan 28, 2016 at 04:06 AM 0
Link

Great, Thank you @Floyd Jones. That was super quick !

Follow this Question

Answers Answers and Comments

29 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

Related Questions

Returns 404 when HTTP is disabled 1 Answer

How to set-up HTTPS certificates for secure connections 1 Answer

What are the best practices in choosing between XML based Proxies vs Node Embedded proxies 1 Answer

How to map the target endpoint URL parameters to the proxy url 4 Answers

HTTP/2 Support in Apigee 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
© 2019 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
  • 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
  • Members
  • Badges