Project

General

Profile

Bug #608

For dataselect code path in WSS, URL specification of format does not correctly configuration file setting

Added by Mike Stults over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
10/02/2014
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

In dataselect code path, the response http type is overriden by the format option when specified in the URL, however, the data processing code uses only the configuration value. The code needs to be updated to use format setting rather than the configuration setting when format (or output) is used in the URL.

History

#1 Updated by Mike Stults over 9 years ago

ready for test, format option selection should be reflected in internal processing flow as well as HTTP response header. Main indicator should be the occurrence of miniseed specific usage log information. Non miniseed options should show writeNormal processing and single line of usage log.

#2 Updated by Chad Trabant over 9 years ago

  • Status changed from New to Resolved

control of the writeMSEED verus writeNormal appears to function correctly based on passed 'format' parameter.

#3 Updated by Robert Weekly over 9 years ago

Slight addendum to Chad's comment...

Based on the entries in dataselect.log, the 'writeMiniSeed' method used by fdsnws-dataselect is invoked by the WSS regardless of whether the 'format' parameter is explicitly defined by the user query.

'writeNormal' continues to be used in the file station.log when using the fdsnws-station ws.

#4 Updated by Robert Weekly over 9 years ago

  • Resolution set to Fixed
  • Status changed from Resolved to Closed

This issue has been addressed. Closing ticket.

Also available in: Atom PDF