<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Compatibility on BIFIT Mitigator</title>
    <link>https://docs.mitigator.ru/v26.04/en/tags/compatibility/</link>
    <description>Recent content in Compatibility on BIFIT Mitigator</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://docs.mitigator.ru/v26.04/en/tags/compatibility/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Compatibility Policy</title>
      <link>https://docs.mitigator.ru/v26.04/en/maintenance/compat/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/maintenance/compat/</guid>
      <description>Update Path A successful upgrade to the next major versions is only guaranteed from the latest minor version of the currently installed major version.
Minor versions within a major version may be skipped during an upgrade.
Example. Given available versions: v12.34.0, v12.34.1, v12.34.2, v12.35.0, v12.35.1.
Guaranteed:
v12.34.2 → v12.35.0 (minor version .2 is the latest of v12.34) v12.34.2 → v12.35.1 (see above, v12.35.0 can be skipped) v12.34.0 → v12.34.2 (v12.34.1 can be skipped) Not guaranteed:</description>
    </item>
    <item>
      <title>Integration</title>
      <link>https://docs.mitigator.ru/v26.04/en/integrate/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/integrate/</guid>
      <description>MITIGATOR has a REST API that allows you to perform any actions in the system. API documentation is included in MITIGATOR &amp;ldquo;Help&amp;rdquo; section. API compatibility in versions follows the policy.
API Usage Examples:
fail2ban integration; FastNetMon integration; black and white lists export from external systems; integration with the hosting control panel; own dashboards. MITIGATOR writes metrics in Graphite.
Game launchers can be authorized on the MITIGATOR using MITIGATOR Challenge Response (MCR) protocol.</description>
    </item>
  </channel>
</rss>