Opened 6 months ago

Closed 6 months ago

#1534 closed defect (fixed)

SECORE Check error with unresolvable CRS from URL with different application name

Reported by: bphamhuu Owned by: bphamhuu
Priority: major Milestone: 9.4
Component: secore Version: development
Keywords: Cc: dmisev, vmerticariu
Complexity: Medium


SECORE's application name is def by default, but if someone wants to deploy with another name like: crs_resolver, it should work as same as default name (e.g: http://localhost:8080/crs_resolver/epsg/0/4326)

Here is an ingredient file which uses SECORE with https and name is def2 and it has error in SECORE.

  "config": {
        "service_url": "http://localhost:8080/rasdaman/ows",
        "tmp_directory": "/tmp/",
        "crs_resolver": "",
        "default_crs": "",
    "mock": false,
    "automated": true
  "input": {
    "coverage_id": "test_AverageChloro",
    "paths": [
  "recipe": {
    "name": "time_series_irregular",
    "options": {
      "time_parameter": {
        "filename": {
          "regex": "(.*)_(.*)\\.(.*)",
          "group": "2"
        "datetime_format": "YYYY-MM"
      "time_crs": "",
      "tiling": "ALIGNED [0:3600, 0:1800, 3]"
 Parsing URI: http://localhost:8080/def/crs/OGC/0/AnsiDate?axis-label=%22t%22
 DEBUG [08:29:39] SecoreServlet@110: Query data from *cache* for URI request: http://localhost:8080/def/crs/OGC/0/AnsiDate?axis-label=%22t%22
 ERROR [08:29:39] EqualityHandler@88: Failed resolving definition: https:/
OperationNotSupported: Can not resolve request:
	at secore.Resolver.resolve(
	at secore.handler.EqualityHandler.handle(

Change History (1)

comment:1 Changed 6 months ago by bphamhuu

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.