<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.rosomakho-httpbis-outdated-proxy-config" target="https://datatracker.ietf.org/doc/html/draft-rosomakho-httpbis-outdated-proxy-config-02">
   <front>
      <title>Detecting Outdated Proxy Configuration</title>
      <author initials="Y." surname="Rosomakho" fullname="Yaroslav Rosomakho">
         <organization>Zscaler</organization>
      </author>
      <date month="March" day="2" year="2026" />
      <abstract>
	 <t>   This document defines a lightweight mechanism that allows explicit
   HTTP proxies to inform clients when their proxy configuration, such
   as a Proxy Auto-Configuration (PAC) file or Provisioning Domain (PvD)
   proxy configuration, is outdated.  Clients signal to the proxy the
   configuration URL and the timestamp of when it was last fetched.  In
   response, the proxy may indicate that a newer version of the
   configuration is available.  This enables clients to refresh their
   configuration without relying on frequent polling or short expiration
   intervals.  The mechanism is designed to be compatible with existing
   proxy deployment models and supports both PAC-based and PvD-based
   configurations.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-rosomakho-httpbis-outdated-proxy-config-02" />
   
</reference>
