y.st./source/pages/en/weblog/2016/03-March/17.xhtml

<?php
/**
 * <https://y.st./>
 * Copyright © 2016 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => 'I&apos;m done with this',
	'body' => <<<END
<p>
	Someone writing on the <a href="https://github.com/curl/curl/issues/716">$a[cURL] bug report page</a> is continuing to justify the stripping of the trailing dot from the $a[HTTP] Host header.
	I thought that I was ready to just call $a[cURL] a lost cause, and continue on my way, but this inability to get through to people that standards should be followed is still getting on my nerves.
	It has prompted me to start making preparations for once I have control of my own clearnet website again.
	I&apos;ve added this to the <code>&lt;VirtualHost/&gt;</code> that serves my non-onion websites:
</p>
<blockquote><pre><code>RewriteEngine On
RewriteCond %{HTTP_HOST} ^(.*[0-9a-z])$ [NC]
RewriteRule ^(.*)\$ https://%1./ [R=301,L]</code></pre></blockquote>
<p>
	This host isn&apos;t reachable from the clearnet aside from on my local network, but tests show that it functions the way that I want it to.
	Screw non-conforming clients.
	This is personal.
	I also built a skeletal 400 page in $a[PHP] that causes the server to send the desired pages to clients even if they send malformed $a[SNI] host names; the catch is that i intentionally didn&apos;t change the $a[HTTP] response code.
	Web clients will still see a 400 error code.
	Some testing on my mother&apos;s machine shows that Internet Explorer refuses to display the page sent if a 400 error code is present, so Internet Explorer won&apos;t be able to see my website.
	I might elaborate on my 400 error page script to make it insert a warning into $a[XHTML] files as well.
	That way viewers will see a message telling them that their Web browser is wonky and will be provided a link to a page detailing all the known Web clients with this issue and links to the bug reports.
	Then again, maybe I won&apos;t even use this 400 error script at all.
	Maybe I&apos;ll just let <a href="apt:apache2">Apache</a> do things the way it does by default, but provide a static 400 error page for it to send explaining the issue.
	Any client that erroneously strips the trailing dot off of the $a[HTTP] Host header will cause itself to go into a redirect loop.
	I can&apos;t help that and it&apos;s not my job to try.
	I&apos;m done with this, at least for now.
</p>
<p>
	I&apos;ve modified the hyperlinks in the copyright sections of my pages on this site to point to the dotted version of my main domain, as well as the copyright section in the comments at the top, as both are in my main template.
	I&apos;ve left old hyperlinks in weblog entries alone for now, mostly because it will be a huge pain to go back and modify all of these links.
	I&apos;ll probably do it eventually though.
</p>
<p>
	I checked back with the place that told me to check back today, and there are no jobs available there.
	I&apos;ve also signed up with the temp agency.
	I found that they don&apos;t actually try to match employees with jobs.
	Instead, they offer job listings that registered users can apply for.
	I&apos;ve applied for three listed jobs.
</p>
END
);