Re: [Fastcgipp-users] FastCGI++ usage for REST service and support for PUT methods

[Matt Schuckmann]

Thanks Eddie, 
That partially solves the problem but inProcessor() is only called if it's a 
POST method, with REST api's data (typically JSON or XML) can be carried with 
PUT methods also.

I'm not sure if you should just inProcessor() called for any in-data or just 
POST and PUT methods. 
My gut says that clients of your library should at least have a chance to 
process any data provided no matter the method and content type. 

Matt S. 

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden
> On Behalf Of Eddie Carle
> Sent: Friday, July 25, 2014 9:58 PM
> To: address@hidden
> Subject: Re: [Fastcgipp-users] FastCGI++ usage for REST service and
> support for PUT methods
> 
> On Fri, 2014-07-25 at 16:10 -0700, Matt Schuckmann wrote:
> > I am testing out using FastCGI++ for an embedded REST service
> > application and it didn't take me long to discover that FastCGI++
> > completely discards content data associated with a PUT method,
> > actually it looks like it only accepts data from POSTs and only
> > requests with a content type of multipart/form-data or
> > application/x-www-form-urlencoded.
> >
> > Is there a reason for this or just an oversight?
> >
> > At this point I'm planning on making the changes for FastCGI++ to
> > properly receive PUT data and any suggestions on how I should proceed
> > would be appreciated.
> 
> Check out Fastcgipp::Request::inProcessor(). It doesn't exist in the
> tarballed versions of fastcgi++ but if you checkout the latest git it
> is there. I think it should allow you to do what you're hoping.
> --
>         Eddie Carle
>