Post request with query string parameters

Question

I'm trying to build a Web API for a complex type of searching. I want to support paging in the results. The "state" of the search is complex, so not really suitable for persisting in the query string. But I'd like for the paging options to be included within the query string.

I've implemented two methods, as below, and the web api code seems to understand what I'm trying to do, but the query string parameters never get assigned. Any hints or advice on this would be appreciated:

public Task<HttpResponseMessage<SearchResults>> Post(SearchRequest request) //Method 1
{
    return Post(request, null, null);
}

public async Task<HttpResponseMessage<SearchResults>> Post(SearchRequest request, string page, string pageSize) //Method 2
{
    //All of the complex code, including...
    if (PageNo < TotalPages)
    {
        searchResults.AddLink(new Link { Uri = Url.Route("DefaultApi", new {
             controller = "AdvancedSearch",
             page = (PageNo + 1).ToString(),
             pageSize = PageSize.ToString() }),
             Relation = "nextPost" });
    }
    //Final wrap up, etc
}

On POSTing a SearchRequest to /api/AdvancedSearch, Method 1 is called, which in turn calls Method 2, which does the search, and packages up the results. As you can hopefully see, included in this result (if more pages of results are available) is a URL to post to for the next page. The generated URL base on this is /api/AdvancedSearch?page=2&pageSize=20, exactly as I'd hoped.

In my calling code, I then perform a POST to this second URL. Only Method 2 is invoked (as expected). But, both page and pageSize are null.

What am I doing wrong? Or what else do you need to see in order to answer this question?

HttpResponseMessage<T> is being dropped so you might need to redesign yours. — Aliostad
– Aliostad, Commented May 9, 2012 at 9:55
@Aliostad - do you have a link to that change? What's the replacement to be? — Damien_The_Unbeliever
– Damien_The_Unbeliever, Commented May 9, 2012 at 10:01
Download the latest from aspnetwebstack.codeplex.com and you will see that latest System.Net.Http.dll does not have it anymore. — Aliostad
– Aliostad, Commented May 9, 2012 at 10:14
I'm having this same problem , am wondering whether its due to using the beta release and not the nightly build? — Tom
– Tom, Commented May 22, 2012 at 16:25
@Tim - I've not managed to move forward from the beta release myself. This was for a prototype and, for the time being, I'm manually populating the parameters inside the function - with the intention to revisit this issue later if the prototype is successful. — Damien_The_Unbeliever
– Damien_The_Unbeliever, Commented May 23, 2012 at 7:36

Aliostad · Accepted Answer · 2012-05-09 15:46:00Z

0

Below is not needed

~~You need to decorate your parameters using [FromUri]:~~

~~public async Task<HttpResponseMessage<SearchResults>> Post(SearchRequest request, [FromUri]string page, [FromUri]string pageSize)~~

As I said in the comments, HttpResponseMessage<T> is being dropped since the Content property of HttpResponseMessage will perform all needed operations.

I checked and I passed querystring params in a post, no problem.

edited May 9, 2012 at 15:46

answered May 9, 2012 at 10:16

Aliostad

81.9k21 gold badges164 silver badges209 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Aliostad Over a year ago

@Damien_The_Unbeliever let me have a look.

Aliostad Over a year ago

@Damien_The_Unbeliever I checked and I passed querystring params in a post, no problem.

Collectives™ on Stack Overflow

Post request with query string parameters

1 Answer 1

Below is not needed

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Below is not needed

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related