Mike Lissner

Another stray, half-finished ticket.

Oh no. Cases can have multiple referring judges? That's....cruel. Aside from fixing this in the parser, we'll need to update CourtListener to handle more than one judge.

FWIW, these are the headers that Digital Ocean's nginx configurator provides (though it lets you twiddle with it): add_header Content-Security-Policy "default-src 'self' http: https: data: blob: 'unsafe-inline'" always;

And, of course, MDN seems to have the best docs about this: https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP

Just checked on prod: ``` ↪ curl -I "https://nmonesource.com/nmos/nmsc/en/nav_date.do?iframe=true" HTTP/1.1 403 403 Date: Tue, 14 May 2019 16:52:28 GMT Content-Type: text/html;charset=utf-8 Content-Length: 3110 Connection: keep-alive Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips Cache-Control:...

:+1:

This scraper can be made now, if somebody wants. It can easily live in Juriscraper without causing any trouble. Just won't go into usage for a while...

This looks great. Thanks Kevin. One other stray thought I had is that we should also be thinking about search relevancy and which fields we'll want to use for that....

We're getting faster at catching this kind of thing!

I think we concluded there's no point in saving these URLs, since they expire anyway. In that case, I think this issue is moot. If so, can we close it?