feat(route): 增加了六个美国博物馆的展讯

[chazeon]

该 PR 相关 Issue / Involved issue

Close #

完整路由地址 / Example for the proposed route(s)

/brooklynmuseum/exhibitions
/brooklynmuseum/exhibitions/current
/brooklynmuseum/exhibitions/upcoming
/brooklynmuseum/exhibitions/past
/metmuseum/exhibitions
/metmuseum/exhibitions/current
/metmuseum/exhibitions/upcoming
/metmuseum/exhibitions/past
/guggenheim/exhibitions
/jewishmuseum/exhibitions
/mcachicago/exhibitions
/newmuseum/exhibitions

新 RSS 检查列表 / New RSS Script Checklist

• 新的路由 New Route
  • 跟随 v2 路由规范 Follows v2 Script Standard
• 文档说明 Documentation
  • 中文文档 CN
  • 英文文档 EN
• 全文获取 fulltext
  • 使用缓存 Use Cache
• 反爬/频率限制 anti-bot or rate limit?
  • 如果有, 是否有对应的措施? If yes, do your code reflect this sign?
• 日期和时间 date and time
  • 可以解析 Parsed
  • 时区调整 Correct TimeZone
• 添加了新的包 New package added
• Puppeteer

说明 / Note

增加了六个美国博物馆的展讯

• 部分 pubDate 设置为了展览开始日
• 部分全文获取有效

[chazeon]

@TonyRL About the insecureHTTPParser: Yesterday I used to get the HPE_INVALID_HEADER_TOKEN error, and adding this insecureHTTPParser option indeed fix the error. Today even after removing this option this error no longer appears. Do you have any idea why I got HPE_INVALID_HEADER_TOKEN earlier?

[TonyRL]

@TonyRL About the insecureHTTPParser: Yesterday I used to get the HPE_INVALID_HEADER_TOKEN error, and adding this insecureHTTPParser option indeed fix the error. Today even after removing this option this error no longer appears. Do you have any idea why I got HPE_INVALID_HEADER_TOKEN earlier?

There are some replies that reported it's an issue with Incapsula CDN in nodejs/node#27711 (comment) and above, though one below said it's not just Incapsula.

Coincident?

$ nslookup www.metmuseum.org
Server:         192.168.1.250
Address:        192.168.1.250#53

Non-authoritative answer:
www.metmuseum.org       canonical name = bhpijji.x.incapdns.net.
Name:   bhpijji.x.incapdns.net
Address: 45.60.83.20

[chazeon]

@TonyRL About the insecureHTTPParser: Yesterday I used to get the HPE_INVALID_HEADER_TOKEN error, and adding this insecureHTTPParser option indeed fix the error. Today even after removing this option this error no longer appears. Do you have any idea why I got HPE_INVALID_HEADER_TOKEN earlier?

There are some replies that reported it's an issue with Incapsula CDN in nodejs/node#27711 (comment) and above, though one below said it's not just Incapsula.

Coincident?

$ nslookup www.metmuseum.org
Server:         192.168.1.250
Address:        192.168.1.250#53

Non-authoritative answer:
www.metmuseum.org       canonical name = bhpijji.x.incapdns.net.
Name:   bhpijji.x.incapdns.net
Address: 45.60.83.20

Good to know. This is likely to be the cause.

[chazeon]

I think all the issues have been resolved. Please take another look.

[TonyRL]

It seems their Incapsula WAF has already blocked me