microsoft / microsoft/winget-pkgs

[New Feature]: Log destination URL

Open
#65,878 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Validation-Pipeline Issue-Feature
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

Description of the new feature/enhancement

With logs being available in the pipeline now, I would like to easily see if a URL is being redirected. Since all of the URLs are checked for domain validation, I believe it should be trivial to add a log of each URL which is being tested, as well as the URL the final result comes from.

PS> Get-UrlResponse 'https://bit.ly/3c899W3' # This is a custom function

Name                           Value
----                           -----
ResponseCode                   200
ResponseUrl                    https://github.com/microsoft/winget-pkgs
Headers                        {Expect-CT, Vary, Server, X-Content-Type-Options...}
Response                       https://github.com/microsoft/winget-pkgs
Url                            https://bit.ly/3c899W3

I know this is easy to do in PowerShell (see above), and I would imagine that logging the tested URL and the response URL for each wouldn't be difficult.

Proposed technical implementation details (optional)

Area-Pipelines / Add a new file to the ValidationResult.zip file with additional URL trace information showing redirects

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.

Research direction

Start in the Area-Pipelines implementation and trace how ValidationResult.zip is produced. Determine where URL validation records the tested URL and final response URL; done means the generated archive contains additional URL trace information for redirects.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
ci-cd, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.