Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

issue-1538-troubled-proxy-parsing #1539

Merged
merged 5 commits into from May 5, 2022
Merged

issue-1538-troubled-proxy-parsing #1539

merged 5 commits into from May 5, 2022

Commits on May 4, 2022

  1. Check for schema during URL parse error handling. Lots of unit tests.

    brian-cook committed May 4, 2022
    Copy the full SHA
    4633ab9 View commit details
    Browse the repository at this point in the history

  2. Update from Check Style failure.

    brian-cook committed May 4, 2022
    Copy the full SHA
    a03207d View commit details
    Browse the repository at this point in the history

  3. Another attempt at cargo fmt.

    brian-cook committed May 4, 2022
    Copy the full SHA
    cc9b090 View commit details
    Browse the repository at this point in the history

  4. Fix a Linux-ism.

    brian-cook committed May 4, 2022
    Copy the full SHA
    5802566 View commit details
    Browse the repository at this point in the history

Commits on May 5, 2022

  1. Introduce BadScheme; an error source. Change schema to scheme. Use Ba… 

    …dScheme instead of the error text to determine that a scheme is not present.
    brian-cook committed May 5, 2022
    Copy the full SHA
    47e331a View commit details
    Browse the repository at this point in the history