<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>big-ip on {bjørn:johansen}</title>
    <link>https://bjornjohansen.com/category/big-ip/</link>
    <description>Recent content in big-ip on {bjørn:johansen}</description>
    <generator>Hugo -- 0.118.2</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 28 Sep 2015 17:09:42 +0000</lastBuildDate>
    <atom:link href="https://bjornjohansen.com/category/big-ip/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WordPress behind Big-IP</title>
      <link>https://bjornjohansen.com/wordpress-behind-big-ip/</link>
      <pubDate>Mon, 28 Sep 2015 17:09:42 +0000</pubDate>
       <guid isPermaLink="false">urn:uuid:61323430-6437-5137-a363-313964663739</guid> 
      <description>To be honest, I don’t exactly know too much about Big-IP, but I’ve come across someone who use it. They terminate HTTPS in Big-IP and WordPress runs on plain HTTP on port 80 on the backend nodes. By default, this makes WordPress confused, so you can’t login to the WordPress dashboard.</description>
    </item>
  </channel>
</rss>
