Format/typo check 2005/mynx
The bugs.md file was updated slightly and so was the thanks file, namely suggesting that it might be possible for further code to be added to the alt code to make it set up https (they already stated that there might be a command line that could get it to work).
This commit is contained in:
1 parent
6ad8c4cb54
commit
cdc75eecec
3 files changed
+40
-28
No files matched your search
+33
-23
@@ -4,6 +4,9 @@
|
||||
make
|
||||
```
|
||||
|
||||
There is an alternate version that scans for (_ONLY_ scans) the string `https`
|
||||
as a starting point. See [alternate code](#alternate-code) below.
|
||||
|
||||
|
||||
### Bugs and (Mis)features:
|
||||
|
||||
@@ -30,32 +33,39 @@ the issue of https.
|
||||
|
||||
```sh
|
||||
./mynx http://www.textfiles.com
|
||||
|
||||
./mynx manual.html
|
||||
```
|
||||
|
||||
|
||||
Some have pointed out that this will not work for https initially
|
||||
for two reasons. For a starting point see the alternate code section below.
|
||||
|
||||
|
||||
## Alternate code:
|
||||
|
||||
As noted this will not work for https. This is because it does not scan for
|
||||
https but also a secure connection needs to be set up before http commands can
|
||||
be sent. One would also have to specify a port in the URL. Fortunately or
|
||||
unfortunately many more websites use https nowadays so this entry will not work
|
||||
as well as it used to. If one were to try and connect to `https://www.ioccc.org`
|
||||
with this entry they'll just get a 301 error.
|
||||
Obviously this will not work with `https` as it only scans for `http` in the URL
|
||||
(if not specified it tries to open it as a local file). But even if it scanned
|
||||
for `https` one would need to do more work as it would have to set up a secure
|
||||
connection before http commands could be sent. Fortunately or unfortunately
|
||||
many more websites use https so this entry will not work as well as it used to.
|
||||
If one were to try and connect to <https://ioccc.org> with this entry they'll
|
||||
just get a 301 error.
|
||||
|
||||
In case someone can come up with a clever pipeline or some other hack or
|
||||
workaround (perhaps [stunnel](https://www.stunnel.org)),
|
||||
The alternate code is a starting point that scans for `https` too (note you have
|
||||
to specify the port in this case) but that is all it does. It will not work with
|
||||
https websites as it does not set up a secure connection. But should anyone wish
|
||||
to either come up with a pipeline (or some other command line) that allows it to
|
||||
work with https or to update the code to support https they may. Otherwise you
|
||||
must just appreciate the entry for what it once was.
|
||||
|
||||
To compile:
|
||||
|
||||
### Alternate build:
|
||||
|
||||
|
||||
```sh
|
||||
make alt
|
||||
```
|
||||
|
||||
|
||||
### Alternate use:
|
||||
|
||||
Use `mynx.alt` as you would `mynx`. You'd have to specify a port at the end of
|
||||
the URL like:
|
||||
|
||||
@@ -84,13 +94,13 @@ it inspired me to try my hand at writing the client side complement.
|
||||
A typical build command would be:
|
||||
|
||||
```sh
|
||||
cc -omynx mynx.c
|
||||
cc -o mynx mynx.c
|
||||
```
|
||||
|
||||
While some others like to be a little different:
|
||||
|
||||
```sh
|
||||
cc -omynx mynx.c -lnsl -lsocket
|
||||
cc -o mynx mynx.c -lnsl -lsocket
|
||||
```
|
||||
|
||||
I even managed to figure out a basic configure script, given last year's
|
||||
@@ -111,14 +121,14 @@ After which, the rest of the documentation can be read by saying:
|
||||
Manifest:
|
||||
|
||||
```
|
||||
mynx.c
|
||||
makefile pre-built generic Unix
|
||||
README.TXT
|
||||
manual.html
|
||||
makefile.in makefile template
|
||||
entities.txt ISO 8859-1 entites
|
||||
configure.in configure script description
|
||||
configure pre-built configure script
|
||||
mynx.c
|
||||
makefile pre-built generic Unix
|
||||
README.md
|
||||
manual.html
|
||||
makefile.in makefile template
|
||||
entities.txt ISO 8859-1 entites
|
||||
configure.in configure script description
|
||||
configure pre-built configure script
|
||||
```
|
||||
|
||||
|
||||
|
||||
@@ -2263,10 +2263,11 @@ for running itself.
|
||||
[Cody Boone Ferguson](/winners.html#Cody_Boone_Ferguson) notes that, though
|
||||
probably obvious, this entry will not work with https. He added an alt version
|
||||
that scans for https in case someone wants to set up a pipeline or other
|
||||
workaround (perhaps with stunnel) but the problem otherwise is a secure
|
||||
connection has to first be set up in order to give http commands. This is not a
|
||||
bug but it's worth pointing out as it won't work on as many websites as it used
|
||||
to including the [IOCCC website](https://www.ioccc.org) itself.
|
||||
workaround (perhaps with stunnel) or even add additional code to it to make it
|
||||
work with https but the problem otherwise is a secure connection has to first be
|
||||
set up in order to give http commands. This is not a bug but it's worth pointing
|
||||
out as it won't work on as many websites as it used to including the [IOCCC
|
||||
website](https://www.ioccc.org) itself.
|
||||
|
||||
|
||||
## 2005 sykes
|
||||
|
||||
+2
-1
@@ -3035,7 +3035,8 @@ needed but part of the entry) would work with compilers that have by default
|
||||
|
||||
Cody also added the alt code which does scan for https. Futile, maybe, based on
|
||||
how https is set up, in which case just enjoy it for what it was. But there
|
||||
might be some command line that will let it work that way.
|
||||
might be some command line that will let it work that way or perhaps someone
|
||||
wants to add the necessary code.
|
||||
|
||||
|
||||
## [2005/persano](2005/persano/persano.c) ([README.md](2005/persano/README.md]))
|
||||
|
||||
Reference in new issue
Block a user