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

Path	csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From	Andy Burns <usenet@andyburns.uk>
Newsgroups	comp.infosystems.www.misc, comp.misc
Subject	Re: no-https: a plain-HTTP to HTTPS proxy
Date	Tue, 18 Sep 2018 20:16:37 +0100
Lines	18
Message-ID	<g0d18mFlsccU1@mid.individual.net> (permalink)
References	<87d0tdgbt4.fsf@violet.siamics.net> <eli$1809161636@qaz.wtf> <87r2hrdk8b.fsf@violet.siamics.net>
Mime-Version	1.0
Content-Type	text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding	7bit
X-Trace	individual.net I2Y+sEUWCJh+vLjdomEIzgZuwpSIh4MWXsbusP09SLQ9Bn4MFm
Cancel-Lock	sha1:XxcSjsBCgv6f05tTYeodvGyqoCc=
User-Agent	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.0
In-Reply-To	<87r2hrdk8b.fsf@violet.siamics.net>
Content-Language	en-GB
Xref	csiph.com comp.infosystems.www.misc:158 comp.misc:16682

Cross-posted to 2 groups.

Show key headers only | View raw

Ivan Shmakov wrote:

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

yes, e.g.

"The attribute name, followed by zero or more space characters, followed 
by a single U+003D EQUALS SIGN character, followed by zero or more space 
characters, followed by the attribute value, which, in addition to the 
requirements given above for attribute values, must not contain any 
literal space characters, any U+0022 QUOTATION MARK characters ("), 
U+0027 APOSTROPHE characters ('), U+003D EQUALS SIGN characters (=), 
U+003C LESS-THAN SIGN characters (<), U+003E GREATER-THAN SIGN 
characters (>), or U+0060 GRAVE ACCENT characters (`), and must not be 
the empty string"

<https://www.w3.org/TR/html5/syntax.html#attribute-names>

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