Racket Docs Website Search Broken
59 views
Skip to first unread message
Leif Andersen
Mar 22, 2018, 1:51:52 PM3/22/18
to racket-dev
It seems like the search feature in the Racket docs is broken. Every
thing I search for (say, struct) causes the connection to fail.
Looking at the url, it looks about what you would expect:
http://docs.racket-lang.org/search/index.html?q=struct
When I remove the `?q=struct`, at the end and just go to:
http://docs.racket-lang.org/search/index.html
then the search page loads fine and I can use the instant search.
Finally, this seems to be only on `docs.racket-lang.org`. My local
docs, for example, seems to be working just fine.
~Leif Andersen
thing I search for (say, struct) causes the connection to fail.
Looking at the url, it looks about what you would expect:
http://docs.racket-lang.org/search/index.html?q=struct
When I remove the `?q=struct`, at the end and just go to:
http://docs.racket-lang.org/search/index.html
then the search page loads fine and I can use the instant search.
Finally, this seems to be only on `docs.racket-lang.org`. My local
docs, for example, seems to be working just fine.
~Leif Andersen
Leandro Facchinetti
Mar 22, 2018, 2:42:31 PM3/22/18
to racket-dev
That’s odd, because it’s working for me:
Leif Andersen
Mar 22, 2018, 2:49:49 PM3/22/18
to Leandro Facchinetti, racket-dev
Very odd. I've had several other people try it on several different
browsers we all can't connect (picture attached).
~Leif Andersen
On Thu, Mar 22, 2018 at 2:42 PM, 'Leandro Facchinetti' via Racket
Developers <racke...@googlegroups.com> wrote:
> That’s odd, because it’s working for me:
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Racket Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-dev+...@googlegroups.com.
> To post to this group, send email to racke...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-dev/869F583F-D93B-4B2C-8F60-E90815E5996F%40leafac.com.
> For more options, visit https://groups.google.com/d/optout.
browsers we all can't connect (picture attached).
~Leif Andersen
On Thu, Mar 22, 2018 at 2:42 PM, 'Leandro Facchinetti' via Racket
Developers <racke...@googlegroups.com> wrote:
> That’s odd, because it’s working for me:
>
>
>
>
> You received this message because you are subscribed to the Google Groups
> "Racket Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-dev+...@googlegroups.com.
> To post to this group, send email to racke...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-dev/869F583F-D93B-4B2C-8F60-E90815E5996F%40leafac.com.
> For more options, visit https://groups.google.com/d/optout.
Leandro Facchinetti
Mar 22, 2018, 3:25:57 PM3/22/18
to racket-dev
I see you’re on Firefox, so I tried it here. It works (see below). Could you all be on the same network, and it’s acting funny?
Sam Tobin-Hochstadt
Mar 22, 2018, 3:34:28 PM3/22/18
to Leandro Facchinetti, racket-dev
It works fine in Firefox for me as well.
Lief, if you open the Network panel in the dev tools in Firefox, can you see what network request is failing, and what the error is?
Also, what happens if you try to fetch that URL with `curl` on the command line?
Sam
On Thu, Mar 22, 2018 at 3:25 PM, 'Leandro Facchinetti' via Racket Developers <racke...@googlegroups.com> wrote:
I see you’re on Firefox, so I tried it here. It works (see below). Could you all be on the same network, and it’s acting funny?
--
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscribe@googlegroups.com.
To post to this group, send email to racke...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/1F8C00FC-A511-4D1C-BC11-8824CAC31E10%40leafac.com.
Ben Greenman
Mar 22, 2018, 3:42:20 PM3/22/18
to Sam Tobin-Hochstadt, Leandro Facchinetti, racket-dev
Curl output:
$ curl -v "http://docs.racket-lang.org/search/index.html?q=struct"
* Trying 104.24.100.149...
* Connected to docs.racket-lang.org (104.24.100.149) port 80 (#0)
> GET /search/index.html?q=struct HTTP/1.1
> Host: docs.racket-lang.org
> User-Agent: curl/7.43.0
> Accept: */*
>
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer
$ curl -v "http://docs.racket-lang.org/search/index.html?q=struct"
* Trying 104.24.100.149...
* Connected to docs.racket-lang.org (104.24.100.149) port 80 (#0)
> GET /search/index.html?q=struct HTTP/1.1
> Host: docs.racket-lang.org
> User-Agent: curl/7.43.0
> Accept: */*
>
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer
Greg Hendershott
Mar 22, 2018, 4:17:11 PM3/22/18
to Ben Greenman, Sam Tobin-Hochstadt, Leandro Facchinetti, racket-dev
FWIW it works for me, too.
Couple random ideas:
1. What if you try using https instead of http?
2. From the headers, I see Cloudflare is involved. Although I don't
know much about it, I think part of what they do is try to prevent
DDOS attacks. Is there any chance they put your network in a penalty
box??
Couple random ideas:
1. What if you try using https instead of http?
2. From the headers, I see Cloudflare is involved. Although I don't
know much about it, I think part of what they do is try to prevent
DDOS attacks. Is there any chance they put your network in a penalty
box??
> --
> You received this message because you are subscribed to the Google Groups "Racket Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+...@googlegroups.com.
> You received this message because you are subscribed to the Google Groups "Racket Developers" group.
> To post to this group, send email to racke...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAFUu9R7To_tg9Obw0qpdyFw_azJSeSc2hdT_%3D3WORbMv-8swaA%40mail.gmail.com.
Greg Hendershott
Mar 22, 2018, 4:33:40 PM3/22/18
to Leif Andersen, Ben Greenman, Sam Tobin-Hochstadt, Leandro Facchinetti, racket-dev
Oh, 1 and 2 were really distinct ideas.
1. I figured if something was mucking with your traffic, HTTPS would
kick it out of the picture. (Assuming "it" is something like an ISP,
organization IT department, etc. Maybe the mucking could still happen
if "it" is state-sponsored, idk.)
2. Cloudflare was a separate idea. It seems less likely they'd be
blocking HTTP but not HTTPS. But...I don't really know.
Anyway, using HTTPS whenever possible is a good idea these days.
There's privacy. There's also security, e.g. you probably don't want
an ISP injecting adware/malware into your web pages.
On Thu, Mar 22, 2018 at 4:21 PM, Leif Andersen <le...@leifandersen.net> wrote:
> Hmm...interesting. If I switch from http to https it suddenly works.
>
> Given that, and the fact that everyone who has reported it as broken
> are at Northeastern's campus, your hypothesis might be right. :/
>
> ~Leif Andersen
>> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAGspUn1TTuU3JQt2AHQqjRegyOt8bcPJUSKwRsaDXX8J4b8yZw%40mail.gmail.com.
1. I figured if something was mucking with your traffic, HTTPS would
kick it out of the picture. (Assuming "it" is something like an ISP,
organization IT department, etc. Maybe the mucking could still happen
if "it" is state-sponsored, idk.)
2. Cloudflare was a separate idea. It seems less likely they'd be
blocking HTTP but not HTTPS. But...I don't really know.
Anyway, using HTTPS whenever possible is a good idea these days.
There's privacy. There's also security, e.g. you probably don't want
an ISP injecting adware/malware into your web pages.
On Thu, Mar 22, 2018 at 4:21 PM, Leif Andersen <le...@leifandersen.net> wrote:
> Hmm...interesting. If I switch from http to https it suddenly works.
>
> Given that, and the fact that everyone who has reported it as broken
> are at Northeastern's campus, your hypothesis might be right. :/
>
> ~Leif Andersen
Neil Van Dyke
Mar 22, 2018, 4:35:24 PM3/22/18
to racket-dev
If there's any "dynamic" component to this running on servers (not just
a non-Racket-based HTTP server serving static files, and the dynamic
happening purely in client-side JS), then I'd check the logs related to
that (process logging, any logging related to the connection between the
machine on which that runs and the frontend server/proxy runs, etc.).
Guessing something in there is more likely to break than Cloudflare
itself or Cloudflare's connectivity with these various people.
If you know how to use Wireshark/tshark/tcpdump, and a bit about TCP
states, (or want to learn) it doesn't hurt to watch that when you
reproduce your connection being rejected. It's easier to debug if you
use an HTTP request rather than HTTPS.
Also would help if you knew which ISPs people having trouble are using
(perhaps broken routes, or broken transparent proxying).
(FWIW, I could fetch this URL fine, from both my EC2 proxy and through
at least one Tor US exit node, the latter of which is usually more
likely to be blocked because it's an exit node or because of abuse. EC2
addresses/blocks sometimes blocked for abuse, as well, though not as
much as Tor exits.)
a non-Racket-based HTTP server serving static files, and the dynamic
happening purely in client-side JS), then I'd check the logs related to
that (process logging, any logging related to the connection between the
machine on which that runs and the frontend server/proxy runs, etc.).
Guessing something in there is more likely to break than Cloudflare
itself or Cloudflare's connectivity with these various people.
If you know how to use Wireshark/tshark/tcpdump, and a bit about TCP
states, (or want to learn) it doesn't hurt to watch that when you
reproduce your connection being rejected. It's easier to debug if you
use an HTTP request rather than HTTPS.
Also would help if you knew which ISPs people having trouble are using
(perhaps broken routes, or broken transparent proxying).
(FWIW, I could fetch this URL fine, from both my EC2 proxy and through
at least one Tor US exit node, the latter of which is usually more
likely to be blocked because it's an exit node or because of abuse. EC2
addresses/blocks sometimes blocked for abuse, as well, though not as
much as Tor exits.)
Neil Van Dyke
Mar 22, 2018, 4:40:55 PM3/22/18
to racket-dev
Oh, and since one of the reports contained info that would rule this
out, but we might be looking at info from multiple independent causes of
failure... when someone has this failing, bring up your Firebug-like
developer tools (pressing F12 will work in some Firefoxes, for example),
and check the Console tab, for JS errors, in addition to the Network
tab, for failed requests that you can see there. You might also want to
disable ad-blockers, NoScript (very messy), etc. just long enough to
reproduce this.
out, but we might be looking at info from multiple independent causes of
failure... when someone has this failing, bring up your Firebug-like
developer tools (pressing F12 will work in some Firefoxes, for example),
and check the Console tab, for JS errors, in addition to the Network
tab, for failed requests that you can see there. You might also want to
disable ad-blockers, NoScript (very messy), etc. just long enough to
reproduce this.
Leif Andersen
Mar 23, 2018, 7:49:22 AM3/23/18
to Greg Hendershott, Ben Greenman, Sam Tobin-Hochstadt, Leandro Facchinetti, racket-dev
Hmm...interesting. If I switch from http to https it suddenly works.
Given that, and the fact that everyone who has reported it as broken
are at Northeastern's campus, your hypothesis might be right. :/
~Leif Andersen
On Thu, Mar 22, 2018 at 4:16 PM, Greg Hendershott
<greghen...@gmail.com> wrote:
Given that, and the fact that everyone who has reported it as broken
are at Northeastern's campus, your hypothesis might be right. :/
~Leif Andersen
On Thu, Mar 22, 2018 at 4:16 PM, Greg Hendershott
<greghen...@gmail.com> wrote:
Reply all
Reply to author
Forward
0 new messages