Implement rewriting without regex expression (for example: (.*) on line end)

[ernado-x]

When we have
"routes": {
"Test1": {
"url": "/Test-0/GetPersons",
"rewrite": "/api/Test/GetPersons",
"host": "10.13.125.167",
"port": 81
}
}

//Test1 /Test-0/GetPersons(.) /api/Test/GetPersons 10.13.125.167 81
the rewrite engine not accept url, but when we change "url" option to "url": "/Test-0/GetPersons(.)" then all works fine.

Can you implement simple syntax when we not need (.*) at end of url.

[tshemsedinov]

Ok, but give me real example where it is needed, this example have no sense, it maps one url to one route, if we do so, config file will turns into list of hundred urls. I'll advise to do it in two following ways instead:

routes: {
Test1: {
url: "/Test-0/(.*)",
rewrite: "/api/Test/[1]",
host: "10.13.125.167",
port: 81
}
}

or so:

routes: {
Test1: {
url: "/Test-0/(GetPersons)",
rewrite: "/api/Test/[1]",
host: "10.13.125.167",
port: 81
}
}

[eagleeye]

But it is a real task to do next forwards, such as
from
http://host1/Test/GetPerson
http://host1/Test/GetPersons
http://host1/Test/GetDataTable
to
http://host2:81/api/Test/GetPerson
http://host2:81/api/Test/GetPersons
http://host2:81/api/Test/GetDataTable

[eagleeye]

i know that example above can be made by simple regexp, but framework should provide ability to do stupid routes also

[ernado-x]

Point of this discussion is to give Eeagleeye ability to create tool for very simple url-route administration. When end user not need to know regexp and he only use tool, but not write expressions.

But now he cannot do this without framework support. Or I'm not quite right?

[tshemsedinov]

Fixed