URIMatch issue, which way to go...

h.hasenack · 2012-10-10 08:53:56

My Unit test uses GUIDstrings for sub-urls. So My SQLModel.Root looks like

LCSServer/{..........}

Unfortunately, the HTTP translates the { into %7B causing the URIMatch to fail.

Obvously, I can change my sources to use a different system for random aliases, but
1) I guess there should be some check in there validating the URI, complaining about invalid characters (Like {, ? and other reserved characters)
2) OR make the URIMatch a bit smarter so it uses the same coding for matching the URI.
3) Or make the HTTPServer translate the html UTI back to a regular URI...?

Regards - Hans

ab · 2012-10-10 09:47:40

Why not just set the "Root" parameter for the model after URI-encoding?

h.hasenack · 2012-10-10 10:10:09

Yes that's a cool way to fix it too.

But.. unfortunately my LCS server supports NamedPipe and Messaging (and later DLL mode), which would probably break my code.
It's also a nice feature to have a more or less readable alias in requests, and generally its not a bad idea to have an Alias restricted a bit like regular identifiers.
In my case, the URI part after the LCSServer/ actually is intended to be a kind of database alias. I dont mind aliases being subject to some validation checks. at all. SO I already implemented a vaslidation check allowing only valid url characters and no special characters.

http://www.blooberry.com/indexdot/html/ … coding.htm

Hans

ab · 2012-10-10 11:58:59

I suspect the Root string property is just a RawUTF8, so for NamedPipe or Messaging, it won't make any difference... but on login.
Why not transform your GUID into a valid path without { or } ?

h.hasenack · 2012-10-10 12:48:34

That's exactly what I did - Ive added URL validation to my alias handler which ensures this problem cannot happen anymore.

mORMot Open Source

#1 2012-10-10 08:53:56

URIMatch issue, which way to go...

#2 2012-10-10 09:47:40

Re: URIMatch issue, which way to go...

#3 2012-10-10 10:10:09

Re: URIMatch issue, which way to go...

#4 2012-10-10 11:58:59

Re: URIMatch issue, which way to go...

#5 2012-10-10 12:48:34

Re: URIMatch issue, which way to go...

Board footer