Parse proxy-style (absolute-url) requests

Open
#1,036 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
networking

Research direction

Start with Tornado's HTTP request parsing path and RFC 2616 section 5.1.2, focusing on requests whose start line contains an absolute URL rather than a leading slash. Done means non-proxy requests with absolute URLs are parsed correctly, with the proxy-style routing compatibility noted in the issue addressed or documented.

Written by the indexing model from the issue text.

Description

httpserver

According to http://tools.ietf.org/html/rfc2616#section-5.1.2 it's valid to use absolute urls in the start line even for non-proxy requests, and servers MUST support it. Tornado needs to parse the url if it doesn't start with a slash (this will need to be messaged for people who are currently writing http proxies with a .* routing rule)

Dominant language
Python
Stars
22.2k
Forks
5.6k
Avg merge
3h 42m
Merged PRs (30d)
16

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tornadoweb/tornado

All issues in tornadoweb/tornado

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.