As you prefer, but for now, you could make it an attribute and add a setter
procedure



On Wed, Mar 27, 2013 at 4:27 PM, colin-adams <notifications@github.com>wrote:

> In library/server/wsf/src/response/wsf_method_not_allowed_response.e:
>
> > @@ -239,8 +260,55 @@ feature {WSF_RESPONSE} -- Output
> >  			res.flush
> >  		end
> >
> > +feature {NONE} -- Implementation
> > +
> > +	recognized_methods: WSF_REQUEST_METHODS
> > +			-- All methods defined in HTTP/1.1 specification
> > +			--| Should this include CONNECT? It probably shouldn't be recognized by an origin server,
> > +			--| We will need a way to extend this for additional methods that the server implements. E.g. PATCH.
>
> I'll comment it all out, to make it easier to keep track of the situation.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/EiffelWebFramework/EWF/pull/46/files#r3552988>
> .
>