Proxy Endpoint HTTP allow method properties not working

Google Cloud Apigee
1

I have following proxy endpoint properties set

/v1/data

true

false

false

false

false

false

false

false

default

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

Thanks, Sanjay

2

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>
2 Likes
3

Dear @skammili , Welcome to Apigee Community :slight_smile: 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.

4

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

1 Like
5

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

6

Removed from the docs. Thanks for the info.

7

Thank you Omid for the aleternate solution.

8

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