HTTP File Search API broken
HTTP File Search API broken
Hi,
Since yesterday 7:35pm UTC the HTTP File Search API returns code 500.
I have already informed connection_problems@oceancolor.sci.gsfc.nasa.gov and they should have raised the issue to the web team, but I prefer post the info here too.
Thanks,
Julien
Copernicus Marine OCTAC Service
Since yesterday 7:35pm UTC the HTTP File Search API returns code 500.
I have already informed connection_problems@oceancolor.sci.gsfc.nasa.gov and they should have raised the issue to the web team, but I prefer post the info here too.
Thanks,
Julien
Copernicus Marine OCTAC Service
Filters:
-
- User Services
- Posts: 16
- Joined: Thu Dec 12, 2024 8:45 am America/New_York
- Has thanked: 1 time
Re: HTTP File Search API broken
Hello,
Thank you for contacting the connection_problems email. Has this team emailed back any helpful insights?
In my own testing, I have not been able to replicate this issue. Sometimes stale settings cause issues with websites. It may help to clear cache, restart the web browser and try accessing the site again. Let us know if you are still having issues.
Thank you for contacting the connection_problems email. Has this team emailed back any helpful insights?
In my own testing, I have not been able to replicate this issue. Sometimes stale settings cause issues with websites. It may help to clear cache, restart the web browser and try accessing the site again. Let us know if you are still having issues.
-
- Posts: 4
- Joined: Thu Jan 10, 2019 9:21 pm America/New_York
Re: HTTP File Search API broken
Just confirming that we're also seeing this issue. This is with wget rather than a web browser so it isn't related to any cache or cookies.
$ wget --post-data="dtype=anc&sensor=aqua&cksum=1&results_as_file=1&search=*P2025007*" https://oceandata.sci.gsfc.nasa.gov/api/file_search
--2025-01-10 12:47:18-- https://oceandata.sci.gsfc.nasa.gov/api/file_search
Resolving oceandata.sci.gsfc.nasa.gov (oceandata.sci.gsfc.nasa.gov)... 169.154.128.84, 2001:4d0:2418:128::84
Connecting to oceandata.sci.gsfc.nasa.gov (oceandata.sci.gsfc.nasa.gov)|169.154.128.84|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2025-01-10 12:47:19 ERROR 500: Internal Server Error.
It's possible something has changed with the way the queries should be structured which I've missed but the "500" code suggests it's more likely a server issue.
Thanks,
Roger.
$ wget --post-data="dtype=anc&sensor=aqua&cksum=1&results_as_file=1&search=*P2025007*" https://oceandata.sci.gsfc.nasa.gov/api/file_search
--2025-01-10 12:47:18-- https://oceandata.sci.gsfc.nasa.gov/api/file_search
Resolving oceandata.sci.gsfc.nasa.gov (oceandata.sci.gsfc.nasa.gov)... 169.154.128.84, 2001:4d0:2418:128::84
Connecting to oceandata.sci.gsfc.nasa.gov (oceandata.sci.gsfc.nasa.gov)|169.154.128.84|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2025-01-10 12:47:19 ERROR 500: Internal Server Error.
It's possible something has changed with the way the queries should be structured which I've missed but the "500" code suggests it's more likely a server issue.
Thanks,
Roger.
Re: HTTP File Search API broken
Hi,
After a deeper analysis I found that wildcards seem broken in the 'search' field, example:
this works:
but this returns error 500:
Do you confirm the issue?
I will try to implement a workaround on our side to no more use wildcards to be able to restart our service.
Is there a way to be notified when there are changes on the File Search API?
Thanks,
Julien
Copernicus Marine OCTAC Service
After a deeper analysis I found that wildcards seem broken in the 'search' field, example:
this works:
Code: Select all
curl -X POST -d "sensor=aqua&dtype=L2&results_as_file=1&sdate=2025-01-10 09:30:00&edate=2025-01-10 09:35:00&search=AQUA_MODIS.20250110T093000.L2.OC.NRT.nc" https://oceandata.sci.gsfc.nasa.gov/api/file_search
Code: Select all
curl -X POST -d "sensor=aqua&dtype=L2&results_as_file=1&sdate=2025-01-10 09:30:00&edate=2025-01-10 09:35:00&search=AQUA_MODIS.*.L2.OC.NRT.nc" https://oceandata.sci.gsfc.nasa.gov/api/file_search
I will try to implement a workaround on our side to no more use wildcards to be able to restart our service.
Is there a way to be notified when there are changes on the File Search API?
Thanks,
Julien
Copernicus Marine OCTAC Service
-
- User Services
- Posts: 16
- Joined: Thu Dec 12, 2024 8:45 am America/New_York
- Has thanked: 1 time
Re: HTTP File Search API broken
Thanks for the additional information. I tried wget also, but did not attempt to use a wildcard character. Let me check to see if that's expected behavior. We can notify the oceancolor mailing list upon changes and bug fixes. Instructions to join are here: https://oceancolor.gsfc.nasa.gov/resources/mailing-lists/
-
- User Services
- Posts: 16
- Joined: Thu Dec 12, 2024 8:45 am America/New_York
- Has thanked: 1 time
Re: HTTP File Search API broken
The issue should be fixed. It was a bug not an enhancement. Thanks for informing us of it. Are you able to get successful results from wget and curl now?
-
- Posts: 4
- Joined: Thu Jan 10, 2019 9:21 pm America/New_York
Re: HTTP File Search API broken
Thanks a lot for the quick fix, I confirm that wildcards work now as expected.