Dear Vijay, Last night, Richard and me together compared your script (simply returned E_SYNTAX) and ours (worked correctly) line by line for at least 10 minutes, and finally figured out there's a extra 's' in your script which inured the problem.
I wonder whether it's reasonable that servers return error code (say E_SYNTAX) PLUS some clues (say, a piece of the string that incurs the problem). I think that benefits clients a lot. Thanks. --Jason On Mon, Nov 5, 2012 at 11:54 PM, Y. Richard Yang <[email protected]> wrote: > Hi Vijay, > > On Mon, Nov 5, 2012 at 9:35 PM, Vijay Gurbani <[email protected]>wrote: > >> Here is the request: >> POST /endpoints/costs HTTP/1.1 >> > > costs -> cost according to spec? > > Richard > > >> Accept: application/alto-endpointcost+json,application/alto-error+json >> Content-Type: application/alto-endpointcostparams+json >> Content-Length: 488 >> >> { >> "constraints": ["le 5", "ge 4"], >> "cost-mode": "numerical", >> "cost-type": "routingcost", >> "endpoints": { >> "dsts": [ >> "ipv4:10.0.0.0", >> "ipv4:15.0.0.0", >> "ipv4:192.168.11.0", >> "ipv4:192.168.10.0", >> "ipv4:128.0.0.0", >> "ipv4:130.0.0.0", >> "ipv4:0.0.0.0", >> "ipv4:132.0.0.0", >> "ipv4:135.0.0.0" >> ], >> "srcs": [ >> "ipv4:10.0.0.0", >> "ipv4:192.168.11.0", >> "ipv4:192.168.10.0" >> ] >> } >> } >> >> and response: >> cat Test-ECS-3.txt | nc p4p-1.cs.yale.edu 6671 >> HTTP/1.1 400 Bad Request >> Content-Length: 24 >> Content-Type: application/alto-error+json >> Date: Tue, 06 Nov 2012 02:47:18 GMT >> >> { >> "code" : "E_SYNTAX" >> } >> > >
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
