-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail to harvest IIS WAF #4827
Comments
A PR is submitted to upstream ckan/ckanext-spatial#337 But we want to stay at current release version and cherry-pick this fix. So we should use our fork in catalog repo's requirement.in. |
Still have issue with harvest source https://hazards.fema.gov/filedownload/metadata/, the harvester does not traverse into folders. It turns out harvester is expecting relative path for each folder, for example, for a WAF like this
Harvester is expecting Nginx and Apache servers are fine. We need to research if IIS is using full path by default, or it is a custom setting by this particular IIS server, and then come up with a fix accordingly. |
Further fix is done to address IIS folder url. |
The fix was merged into upstream main. But it breaks for Apache servers. |
new PR pushed to upstream for fix IIS/APACHE. test added. |
Fail to harvest source https://hazards.fema.gov/filedownload/metadata/. Something to do with ckan/ckanext-spatial#319. Need to exam the iis parser and make it more inclusive.
How to reproduce
harvest IIS WAF with subfolders like this
Expected behavior
traverse into
mydir
and harvest files under the sub folderActual behavior
ignore files under
mydir
Sketch
[Notes or a checklist reflecting our understanding of the selected approach]
The text was updated successfully, but these errors were encountered: