Raalte railway station
Raalte is a railway station located in Raalte, Netherlands. The station originally opened on 1 January 1881 and is located on the Zwolle–Almelo railway. The train services are currently operated by Keolis Nederland. Between 1910 and 1935, there was also a railway line between Deventer and Ommen which crossed the Zwolle–Almelo railway at Raalte.
Raalte | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
![]() | |||||||||||
Location | Netherlands | ||||||||||
Coordinates | 52°23′27″N 6°16′43″E | ||||||||||
Line(s) | Zwolle–Almelo railway | ||||||||||
History | |||||||||||
Opened | 1 January 1881 | ||||||||||
Services | |||||||||||
| |||||||||||
Location | |||||||||||
![]() ![]() Raalte Location within Netherlands |
Train services
Route | Service type | Operator | Notes |
---|---|---|---|
Zwolle - Almelo - Hengelo - Enschede | Local ("Stoptrein") | Keolis Nederland | 2x per hour |
Bus services
Line | Route | Operator | Notes |
---|---|---|---|
162 | Raalte - Lemelerveld - Dalfsen | Syntus Overijssel | Mon-Fri only. |
165 | Raalte - Pleegste - Wesepe - Schalkhaar - Deventer | Syntus Overijssel | |
166 | Raalte - Heino - Lenthe - Wijthmen - Zwolle | Syntus Overijssel | Mon-Fri only. One morning run is operated with a coach type of bus. |
513 | Nijverdal - Haarle - Raalte | Twents | 1x 1,5 hour - no service on evenings and weekends. |
516 | Olst - Boskamp - Eikelhof - Wesepe - Heeten - Raalte | Syntus Overijssel | 1x 90 min - No service on evenings and Sundays. |
563 | Raalte - Broekland - Tongeren - Wijhe | Syntus Overijssel | No service on evenings and Sundays. |
gollark: This is weird. I may be capturing wrong, or... Firefox just isn't actually sending any requests to make the websocket?
gollark: I tried looking at it in Firefox's network pane in the debug thing, the websocket connection just doesn't show. I also tried mitmproxy, which also doesn't show anything. Now I'm trying wireshark, but I don't know how to work that, though it seems to show discord opening websockets okay.
gollark: I know websockets don't work with HTTP2 because it doesn't support protocol upgrade, but as far as I know it should just use HTTP 1.1, and Chrome does this.
gollark: <@!690636955108638740> I think it's enabled, why?
gollark: This is EXTREMELY ANNOYING. I have a bunch of websocket-based things which work fine in Chromium and wscat and whatever else, and appear to work if I run them locally too, but if I both have them behind my reverse proxy (caddy) and use them in Firefox it fails and just says `Firefox can’t establish a connection to the server at wss://[the things]`.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.