Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. Web Development
  3. ASP.NET
  4. IIS returns Bad Request (400) error [modified]

IIS returns Bad Request (400) error [modified]

Scheduled Pinned Locked Moved ASP.NET
helpcomwindows-adminworkspace
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    progan
    wrote on last edited by
    #1

    Hi all! I have such problem with IIS 6.0 configuration. I have a web site with HttpHandler inherited class which catch all requests. When I publish this site on IIS 6.0 and try to launch this application by entering "http://mydomain.com/test-www;par@act=value&Parameter=mypar" my site doesn't catch this request and IIS returns Bad Request (400) error May be RFC 1738 Url Standard works here and IIS can't obtain such requests. But may be there is a way to solve this problem Thank you very much in advance -- modified at 4:42 Thursday 29th November, 2007

    J 1 Reply Last reply
    0
    • P progan

      Hi all! I have such problem with IIS 6.0 configuration. I have a web site with HttpHandler inherited class which catch all requests. When I publish this site on IIS 6.0 and try to launch this application by entering "http://mydomain.com/test-www;par@act=value&Parameter=mypar" my site doesn't catch this request and IIS returns Bad Request (400) error May be RFC 1738 Url Standard works here and IIS can't obtain such requests. But may be there is a way to solve this problem Thank you very much in advance -- modified at 4:42 Thursday 29th November, 2007

      J Offline
      J Offline
      Jim Conigliaro
      wrote on last edited by
      #2

      IIS 6 has a wildcard mapping setting that is designed specifically to process requests that don't map to a specific file (i.e. a request with no file extension). When you configure your web site/app, click on the configuration button under the application settings. Under the application mappings, you should see a wildcard mappings section as well. Map the wildcard request to the aspnet_isapi.dll and make sure that it doesn't require that the file exist. That should solve your problem.

      Jim Conigliaro jconigliaro@ieee.org
      http://www.jimconigliaro.com

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups