Opened 8 years ago

Last modified 8 years ago

#1422 closed defect

Petascope_Parsing CRS is invalid with "https" in domain and left a invalid crs in ps_crs — at Version 1

Reported by: Bang Pham Huu Owned by: Bang Pham Huu
Priority: major Milestone: 9.3
Component: petascope Version: development
Keywords: Cc: Dimitar Misev, Vlad Merticariu
Complexity: Medium

Description (last modified by Bang Pham Huu)

Example:

<ows:ExceptionText>https://www.foodie-cloud.org/def/crs/EPSG/0/3035 definition seems not valid.</ows:ExceptionText>

it is invalid due to https in URL. Also, after wcst_import failed with a recipe which uses this URL as default_crs, it stored an invalid CRS (%SECORE_URL%/crs/) in ps_crs and make another kind of error

 <ows:Exception exceptionCode="InvalidMetadata">
        <ows:ExceptionText>http://localhost:8080/def/crs/// definition seems not valid.</ows:ExceptionText>
    </ows:Exception>

this need a workaround to allow user to delete the error coverage which contains the error URL CRS before try to reingest new coverage with fixed error.

Change History (1)

comment:1 by Bang Pham Huu, 8 years ago

Description: modified (diff)
Summary: Petascope_Parsing CRS is invalid with "-" in domain → Petascope_Parsing CRS is invalid with "https" in domain and left a invalid crs in ps_crs
Note: See TracTickets for help on using tickets.