asp.net mvc - Mvc HttpGetAttribute is accepting Http POST requests -


Does anybody know whether the [HttpGet] attribute is ignored? / P>

I have a controller which is defined on [http gate] , which means that only GET requests are allowed and POST requests are generally rejected with 404 have been done. This action, locally under IIS, is capable of accepting the HTP POST request on the test server, but this is not the case of how it should be. It looks like we need to support post requests on controller tasks and we will add support for it.

However, it raises the question that why IIS is accepting requests under the local copy of the site, I hope that 404 get rejected with the status of the HTPP. Apart from this, we have other sites running on the test server that are behaving just like my local server.

I am not sure that there is something to do with this fact that the request is actually redirected to the request 'main site / portal' is an old ASP.NET web application application which is then the other 'routing' ASP.NET redirects the MVC 3 web application, which will route the request again on the basis of Business Logic's 1 3 other channels. ASP.NET MVC 3 web application All channels essentially provide the same function but there is a slightly different business logic within them. Each channel has a landing controller that will redirect the user to the page where they should go. And this is the action on those lading controllers who have the [HttpGet] attribute.

1 of the following is on the test server on the 3 servers:

  • The user clicks on a button
  • posted on the 'portal' site Request request to post on the 'routing' site in 302. The request to post 'routing' from channel 302 to 'channel' site
  • Post request 404 for 'channel' site results it happens.

    The following is a 2o channel which is on the other 2 channels on the test server and on all 3 channels on your local server:

    1. The user clicks on a button
    2. Posting request 302 in the 'Portal' site 'Routing' site '
    3. Requesting to post to' Routing 'site in 302 on' Channel 'site. >
    4. The 'channel' site on the destination page in Site 302, which requests the posting on the 'Channel' site.
    5. Post request on 200 and generation page for 'channel' for destination page results. UPDATE: This tells me that I'm well and actually led the garden path. The requested redirects are being done through HTT GET and there is no HTP post because the correct behavior for 302 Redirects is. However IE Developer Tools displays as POST requests instead of incorrect requests. It has been found that the channel server was not deployed to test.

      Enter image details here

      < Div class = "post-text" itemprop = "text">

      A HTTP method with a POST method / verb will result in an HTTP response with a 302 status, with a GET method / verb, a new HTTP Request means that a redirect will be successful for an action on a controller with the [HttpGet] attribute.

  • Comments

    Popular posts from this blog

    Pass DB Connection parameters to a Kettle a.k.a PDI table Input step dynamically from Excel -

    multithreading - PhantomJS-Node in a for Loop -

    c++ - MATLAB .m file to .mex file using Matlab Compiler -