Opened 7 months ago

Closed 6 months ago

#1427 closed defect (fixed)

Petascope_Handle POST request for WCS, WCPS in PetascopeInterface without encoded.

Reported by: bphamhuu Owned by: bphamhuu
Priority: major Milestone: 9.3
Component: petascope Version: development
Keywords: Cc: dmisev, vmerticariu, pbaumann
Complexity: Medium

Description

Current WCPS queries in system test need to be using POST to send requests (as some query is big and cannot send by GET) into WcpsServlet? (/ows/wcps). The query also need to be encoded (using xxd) and so on.

The problem is current PetascopeInterface? only support GET request (KVP, REST) correctly and it will have errors as cannot parse parameters from POST requests.

so PetacopeInterface? should parse request in POST with parameters as same as parse GET request (current it parse params map empty).

Attachments (1)

08-059r4_WCS_Extension_-_Processing_2013-12-26.zip (186.9 KB) - added by pbaumann 7 months ago.
WCS Processing Extension 1.0

Download all attachments as: .zip

Change History (7)

comment:1 follow-up: Changed 7 months ago by dmisev

POST is reserved for XML requests as far as I know. The protocol bindings are GET/KVP and POST/XML.

comment:2 in reply to: ↑ 1 Changed 7 months ago by bphamhuu

Replying to dmisev:

POST is reserved for XML requests as far as I know. The protocol bindings are GET/KVP and POST/XML.

it would be good if it can parse a POST request with big WCPS query in KVP as well.

comment:3 Changed 7 months ago by dmisev

  • Cc pbaumann added

Handling KVP in a POST request is not foreseen by the WCS standard AFAIK.

comment:4 Changed 7 months ago by pbaumann

it is foreseen indeed, in the WCS Processing Extension, I attach it here. So this ticket might be considered a feature request.

Changed 7 months ago by pbaumann

WCS Processing Extension 1.0

comment:5 Changed 6 months ago by bphamhuu

  • Milestone changed from 10.0 to 9.3
  • Owner set to bphamhuu
  • Status changed from new to assigned

comment:6 Changed 6 months ago by bphamhuu

  • Resolution set to fixed
  • Status changed from assigned to closed

the patch was applied, and the POST request in KVP can be sent by curl like this and Petascope can parse the KVP request in POST.

  url="http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1&request=ProcessCoverages"
  kvpValues='query=.......'
  curl -s -X POST "$url" --data-urlencode "$kvpValues"
Note: See TracTickets for help on using tickets.