Project

General

Profile

Bug #883

Exception handling does not include http header as defined by corsEnabled property

Added by Mike Stults over 7 years ago. Updated almost 7 years ago.

Status:
New
Priority:
Normal
Assignee:
Mike Stults
Target version:
2.4
Start date:
03/27/2017
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

This issue is identified at Caltech by aparna Bhaskaran. WSS 1.1.8, when their user does a successful query, they get the respective results, when there is no data (resulting in exception handling) the user gets an HTTP message about CORS violation rather than a standard FDSN error message. It looks like WSS exception handling needs to respect the corsEnabled property like successful queries do.

History

#1 Updated by Mike Stults over 7 years ago

  • Resolution set to Fixed

git commit -m "issue 883, make error handling behave like regular handling according to state of corsEnabled property"
[master 5069f32]

#2 Updated by Mike Stults almost 7 years ago

  • Target version set to 2.4

Also available in: Atom PDF