Groups | Search | Server Info | Login | Register

Groups > comp.infosystems.www.misc > #153

Re: no-https: a plain-HTTP to HTTPS proxy

Cross-posted to 2 groups.

Show all headers | View raw

>>>>> Rich <rich@example.invalid> writes:
>>>>> In comp.misc Ivan Shmakov <ivan@siamics.net> wrote:

[...]

 >> OTOH, I don't think I've ever seen the " = " form; do the blanks
 >> around the equals sign even conform to any HTML version?

 > The HTML spec does not appear to explicitly exclude use of spaces
 > around the equals sign.  So unless there is an explicit exclusion
 > somewhere that I've missed, it would be legal to add spaces around
 > the equals.

	Does it explicitly allow spaces?

 > The fact is, even ignoring the spaced equals item, that HTML is
 > "flexible" enough that if you get to the point of wanting to do
 > rewriting/editing that you'll have way less "pull your hair out"
 > issues if you make use of an HTML parser to parse the HTML instead of
 > trying to do anything by string or regex search/replace on the HTML.
 > Anything string/regex search based on HTML will appear to work ok
 > until the day it hits a legal bit of HTML it was not designed to
 > handle, then it will break badly.

 > I. e., the "edge conditions" are so numerous that you are better off
 > using a parser that has already been designed to handle those edge
 > conditions.

	I tend to agree with the above for the general case: where I'd
	expect the code to /fail/ if it encounters something it does not
	understand.

	In this case, something that the code does not understand is
	ought to be left untouched, and I'm unsure if I can readily get
	an HTTP parser that does that.

-- 
FSF associate member #7257  http://am-1.org/~ivan/

Back to comp.infosystems.www.misc | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

no-https: a plain-HTTP to HTTPS proxy Ivan Shmakov <ivan@siamics.net> - 2018-09-16 07:07 +0000
  Re: no-https: a plain-HTTP to HTTPS proxy not@telling.you.invalid (Computer Nerd Kev) - 2018-09-16 22:52 +0000
    Re: no-https: a plain-HTTP to HTTPS proxy Mike Spencer <mds@bogus.nodomain.nowhere> - 2018-09-19 17:27 -0300
  Re: no-https: a plain-HTTP to HTTPS proxy Ivan Shmakov <ivan@siamics.net> - 2018-09-18 13:10 +0000
    Re: no-https: a plain-HTTP to HTTPS proxy Ivan Shmakov <ivan@siamics.net> - 2018-09-18 17:05 +0000
      Re: no-https: a plain-HTTP to HTTPS proxy Andy Burns <usenet@andyburns.uk> - 2018-09-18 18:32 +0100
      Re: no-https: a plain-HTTP to HTTPS proxy Rich <rich@example.invalid> - 2018-09-18 18:56 +0000
        Re: no-https: a plain-HTTP to HTTPS proxy Ivan Shmakov <ivan@siamics.net> - 2018-09-19 05:15 +0000
    Re: no-https: a plain-HTTP to HTTPS proxy Marko Rauhamaa <marko@pacujo.net> - 2018-09-18 22:02 +0300
      Re: no-https: a plain-HTTP to HTTPS proxy Rich <rich@example.invalid> - 2018-09-18 19:08 +0000
    Re: no-https: a plain-HTTP to HTTPS proxy Andy Burns <usenet@andyburns.uk> - 2018-09-18 20:16 +0100
  Re: no-https: a plain-HTTP to HTTPS proxy Ivan Shmakov <ivan@siamics.net> - 2018-09-25 18:39 +0000
    Re: no-https: a plain-HTTP to HTTPS proxy Eli the Bearded <*@eli.users.panix.com> - 2018-09-25 22:29 +0000
      Re: no-https: a plain-HTTP to HTTPS proxy Ivan Shmakov <ivan@siamics.net> - 2018-09-26 01:05 +0000
        Re: no-https: a plain-HTTP to HTTPS proxy Ivan Shmakov <ivan@siamics.net> - 2018-10-04 20:07 +0000
          Re: no-https: a plain-HTTP to HTTPS proxy not@telling.you.invalid (Computer Nerd Kev) - 2018-10-05 00:11 +0000

csiph-web