Hans,
Mea Culpa! Yes, for that test, my test client accidentally sent an
invalid mode as well as an invalid constraint. I never noticed because my
server checks constraints before checking mode.
The test client should be fixed now.
Thanks for spotting that!
- Wendy Roome
On 08/28/2015, 05:15, "Hans Seidel" <[email protected]> wrote:
>Hi Wendy, Hi All
>
>thanks for the client. It helped me a lot to improve our ALTO server.
>One issue I could not solve is the following:
>
>FAILED FCM def-nm-costs-rtg-num:invalid-cost-constraints
>**** incorrect field 'cost-type/cost-mode' in error message
>**** incorrect value 'numeric' in error message
>
>Your client sends a FCM request with cost-mode 'numeric'. I checked the
>RFC and it seems to me that 'numeric' is not a valid cost mode. If I am
>not mistaken it should be either 'num' or 'numerical'.
>
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
