<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Update on Holyarmy.org</title>
		<link>https://holyarmy.org/tags/update/</link>
		<description>Recent content in Update on Holyarmy.org</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Thu, 11 Dec 2008 06:44:45 +0000</lastBuildDate>
		
			<atom:link href="https://holyarmy.org/tags/update/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Logins with mod_rewrite, Cookies, and Javascript Redux</title>
				<link>https://holyarmy.org/2008/12/logins-with-mod_rewrite-cookies-and-javascript-redux/</link>
				<pubDate>Thu, 11 Dec 2008 06:44:45 +0000</pubDate>
				<guid>https://holyarmy.org/2008/12/logins-with-mod_rewrite-cookies-and-javascript-redux/</guid>
				<description>&lt;p&gt;A while back I posted a &lt;a href=&#34;https://holyarmy.org/2008/02/logins-with-mod_rewrite-cookies-javascript/&#34;&gt;simple solution for restricting website access&lt;/a&gt; in a situation where HTTP basic authentication couldn’t be used.&lt;/p&gt;&#xA;&lt;p&gt;Not much more to the story, but I did make a few tweaks to my sample code. The mod_rewrite rule and javascript have been a tiny bit improved, so now after a successful login, it will try to redirect you to where you intended to go. (Previously, it always sent the user to /) &lt;/p&gt;</description>
			</item>
	</channel>
</rss>
