Detecting Outdated Proxy Configuration

Dear HTTP enthusiasts,

Thank you for the constructive discussion of the Detecting Outdated Proxy
Configuration proposal at the IETF123 meeting.

I have published an updated version of the draft that incorporates two of
the most straightforward suggestions:
- Mechanism is now explicitly scoped to HTTP proxying methods that
clearly separate client headers intended for the proxy from those intended
for the destination server.
- The url parameter in Proxy-Config header may be omitted not only for
well-known PvD URL but also for configurations provisioned via mechanisms
that are not associated with a URL such as enterprise device management and
local policy engine.

I'd be very interested in additional feedback and suggestions from the
working group.

Thank you!

Best Regards,
Yaroslav

---------- Forwarded message ---------
A new version of Internet-Draft
draft-rosomakho-httpbis-outdated-proxy-config-01.txt has been successfully
submitted by Yaroslav Rosomakho and posted to the
IETF repository.

Name:     draft-rosomakho-httpbis-outdated-proxy-config
Revision: 01
Title:    Detecting Outdated Proxy Configuration
Date:     2025-09-05
Group:    Individual Submission
Pages:    9
URL:
https://www.ietf.org/archive/id/draft-rosomakho-httpbis-outdated-proxy-config-01.txt
Status:
https://datatracker.ietf.org/doc/draft-rosomakho-httpbis-outdated-proxy-config/
HTML:
https://www.ietf.org/archive/id/draft-rosomakho-httpbis-outdated-proxy-config-01.html
HTMLized:
https://datatracker.ietf.org/doc/html/draft-rosomakho-httpbis-outdated-proxy-config
Diff:
https://author-tools.ietf.org/iddiff?url2=draft-rosomakho-httpbis-outdated-proxy-config-01

Abstract:

   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.



The IETF Secretariat

-- 


This communication (including any attachments) is intended for the sole 
use of the intended recipient and may contain confidential, non-public, 
and/or privileged material. Use, distribution, or reproduction of this 
communication by unintended recipients is not authorized. If you received 
this communication in error, please immediately notify the sender and then 
delete all copies of this communication from your system.