Back to Questions
608
views1
comment
Strange routing when query parameter has wrong case
websharper

I have the following endpoint:

1

| [<EndPoint "GET /storebrowse"; Query("genre")>] StoreBrowse of Genre: string

This doesn't work with the URL that I would expect to work:

http://localhost:9000/storebrowse?genre=zyx

However, I accidentally found out that the following wrong URL will trigger this endpoint:

http://localhost:9000/storebrowse/genre=zyx

This will result in the following wrong value for Genre:

"genre%3Dzyx"

The problem is that the "genre" string and the Genre: string doesn't have the same case in the source. (At runtime, in the browser, it makes no difference.) Changing the first "g" to either lowercase or uppercase in both places will make the endpoint work as expected. The value of Genre will then be only "zyx".

I have only used WebSharper for one hour, so I'm no expert. Did I find a bug, or is this by design, in which case I don't see why. Shouldn't the Query attribute be case ignorant, and shouldn't a wrong URL not be let through?

.

This is by design. The argument to Query is the name of the argument. Arguments whose name is not in any attribute such as Query, Json or FormData are parsed as path fragments. This is to allow you to do things like:

1

| [<EndPoint "GET /storebrowse"; Query("genre")>] StoreBrowse of genre: string * page: int

This parses URLs such as /storebrowse/12?genre=xyz.

By on 9/17/2015 1:29 AM ()

    Topic tags

    IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
    Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy     		Built with WebSharper