EigenDA Proxy returns HTTP status code 200 when using a malformat commitment

[adam-xu-mantle]

Problem

In the EigenDA Proxy get, for some commitments with incorrect formats, the api still returns a status code of 200. This may mislead the users of the EigenDA Proxy.

• GET

curl -v http://127.0.0.1:3100/get/0x0100001  

*   Trying 127.0.0.1:3100...
* Connected to 127.0.0.1 (127.0.0.1) port 3100
> GET /get/0x0100001 HTTP/1.1
> Host: 127.0.0.1:3100
> User-Agent: curl/8.4.0
> Accept: */*
> 
< HTTP/1.1 200 OK
< Date: Sat, 08 Feb 2025 08:09:53 GMT
< Content-Length: 0
< 
* Connection #0 to host 127.0.0.1 left intact

• PUT

curl -v http://127.0.0.1:3100/put/0x00001 -d 'v1.6.3 test'

*   Trying 127.0.0.1:3100...
* Connected to 127.0.0.1 (127.0.0.1) port 3100
> POST /put/0x00001 HTTP/1.1
> Host: 127.0.0.1:3100
> User-Agent: curl/8.4.0
> Accept: */*
> Content-Length: 16
> Content-Type: application/x-www-form-urlencoded
> 
< HTTP/1.1 200 OK
< Date: Sat, 08 Feb 2025 09:17:30 GMT
< Content-Length: 0
< 
* Connection #0 to host 127.0.0.1 left intact

Proposed Solution

Using regular expressions to validate the content of routingVarNamePayloadHex.
"{"+routingVarNamePayloadHex+":(?:[0-9a-fA-F]{2})*}"