Unlike #636 and #635, the state did not update the WARN page location, rather, it appears we're adding an extraneous slash to the URL, e.g. https://dlt.ri.gov//employers/worker-adjustment-and-retraining-notification-warn, which causes the first page we hit to be a 302 found HTTP redirect to https://dlt.ri.gov/employers/worker-adjustment-and-retraining-notification-warn. We hit a second redirect when we fetch the Excel file, because that shares the same base URL. This is handled transparently by the scraper and therefore works, but it causes twice as many HTTP requests as we really need, and strikes me as just bad hygiene to leave in now that we know about it.
Unlike #636 and #635, the state did not update the WARN page location, rather, it appears we're adding an extraneous slash to the URL, e.g.
https://dlt.ri.gov//employers/worker-adjustment-and-retraining-notification-warn, which causes the first page we hit to be a 302 found HTTP redirect tohttps://dlt.ri.gov/employers/worker-adjustment-and-retraining-notification-warn. We hit a second redirect when we fetch the Excel file, because that shares the same base URL. This is handled transparently by the scraper and therefore works, but it causes twice as many HTTP requests as we really need, and strikes me as just bad hygiene to leave in now that we know about it.