🕵️
305
Use Proxy

Example HTTP Response

HTTP Response
HTTP/1.1 305 Use Proxy
Location: http://proxy.example.com:8080
Common Causes
  • Resource requires proxy access (historical)
  • Network configuration mandating proxy
  • Legacy system requirements
Technical Details

What does this mean?

Talk to my agent! This resource insists you go through a middleman. But heads up — this code is retired due to security drama.

Technical Definition

The requested resource must be accessed through the proxy given by the Location header. Deprecated due to security concerns.

RFC Says

"The 305 (Use Proxy) status code was defined in a previous version of this specification and is now deprecated."

Plain English:

This status code is deprecated and should not be used. It was originally intended to force clients to use a specific proxy, but this created security vulnerabilities. Modern applications should not implement or use 305.

Common Misinterpretation

Some developers might think this is still valid for proxy configurations. Don't use it - it's been deprecated due to security concerns and is not supported by modern clients.

Code Snippets

Ready-to-use code for returning this HTTP status in your application:

Node.js
// Express.js
app.get('/example', (req, res) => {
  res.status(305).json({
    error: 'Use Proxy',
    message: 'Your error message here'
  });
});

// Native HTTP
const http = require('http');

http.createServer((req, res) => {
  res.writeHead(305, { 'Content-Type': 'application/json' });
  res.end(JSON.stringify({
    error: 'Use Proxy',
    message: 'Your error message here'
  }));
}).listen(3000);