├── .github ├── FUNDING.yml ├── ISSUE_TEMPLATE │ ├── bug_report.md │ └── feature_request.md ├── dependabot.yml └── workflows │ └── push.yml ├── .gitignore ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── connection.go ├── cookies.go ├── dump.go ├── example ├── headers │ └── headers.go ├── http2 │ └── http2.go ├── ja3 │ └── ja3.go └── proxy │ └── proxy.go ├── example_test.go ├── go.mod ├── go.sum ├── header.go ├── http2.go ├── http3.go ├── ja3.go ├── logger.go ├── pinner.go ├── presets.go ├── profiles.go ├── proxy.go ├── quic_dialer.go ├── redirect.go ├── request.go ├── response.go ├── sesion_http3.go ├── session.go ├── socks5_udp.go ├── structs.go ├── test ├── compression_test.go ├── connection_test.go ├── cookies_test.go ├── header_test.go ├── http2_test.go ├── http3_test.go ├── ja3_test.go ├── pinner_test.go ├── proxy_test.go ├── redirect_test.go ├── request_test.go ├── response_test.go ├── session_test.go ├── utils_test.go ├── verbose_test.go └── websocket_test.go ├── transport.go ├── utils.go └── websocket.go /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | buy_me_a_coffee: noste 2 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | Steps to reproduce the behavior: 15 | 16 | 17 | **Expected behavior** 18 | A clear and concise description of what you expected to happen. 19 | 20 | **Screenshots** 21 | If applicable, add screenshots to help explain your problem. 22 | 23 | 24 | **Desktop (please complete the following information):** 25 | - OS: [e.g. iOS] 26 | - Browser [e.g. chrome, safari] 27 | - Version [e.g. 22] 28 | 29 | **Additional context** 30 | Add any other context about the problem here. 31 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Is your feature request related to a problem? Please describe.** 11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 12 | 13 | **Describe the solution you'd like** 14 | A clear and concise description of what you want to happen. 15 | 16 | **Describe alternatives you've considered** 17 | A clear and concise description of any alternative solutions or features you've considered. 18 | 19 | **Additional context** 20 | Add any other context or screenshots about the feature request here. 21 | -------------------------------------------------------------------------------- /.github/dependabot.yml: -------------------------------------------------------------------------------- 1 | version: 2 2 | updates: 3 | - package-ecosystem: gomod 4 | directory: / 5 | schedule: 6 | interval: weekly 7 | - package-ecosystem: github-actions 8 | directory: / 9 | schedule: 10 | interval: weekly 11 | -------------------------------------------------------------------------------- /.github/workflows/push.yml: -------------------------------------------------------------------------------- 1 | name: build 2 | 3 | on: push 4 | 5 | jobs: 6 | build: 7 | runs-on: ubuntu-latest 8 | steps: 9 | - uses: actions/checkout@v4 10 | - name: Setup Go 11 | uses: actions/setup-go@v5 12 | with: 13 | go-version: '1.24' 14 | 15 | - name: Run Tests 16 | run: | 17 | go test -v ./test -covermode=count -coverpkg=./... -coverprofile=coverage.txt 18 | env: 19 | SECURE_PROXY: ${{ secrets.SECURE_PROXY }} 20 | NON_SECURE_PROXY: ${{ secrets.NON_SECURE_PROXY }} 21 | SOCKS5_PROXY: ${{ secrets.SOCKS5_PROXY }} 22 | 23 | - name: Upload coverage reports to Codecov 24 | uses: codecov/codecov-action@v5 25 | with: 26 | token: ${{ secrets.CODECOV_TOKEN }} 27 | slug: Noooste/azuretls-client -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # If you prefer the allow list template instead of the deny list, see community template: 2 | # https://github.com/github/gitignore/blob/main/community/Golang/Go.AllowList.gitignore 3 | # 4 | # Binaries for programs and plugins 5 | *.exe 6 | *.exe~ 7 | *.dll 8 | *.so 9 | *.dylib 10 | 11 | # Test binary, built with `go test -c` 12 | *.test 13 | 14 | # Output of the go coverage tool, specifically when used with LiteIDE 15 | *.out 16 | 17 | # Dependency directories (remove the comment below to include it) 18 | # vendor/ 19 | 20 | # Go workspace file 21 | go.work 22 | 23 | .idea 24 | .run -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | noste@azureaio.com. 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series 86 | of actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or 93 | permanent ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within 113 | the community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.0, available at 119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 120 | 121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 122 | enforcement ladder](https://github.com/mozilla/diversity). 123 | 124 | [homepage]: https://www.contributor-covenant.org 125 | 126 | For answers to common questions about this code of conduct, see the FAQ at 127 | https://www.contributor-covenant.org/faq. Translations are available at 128 | https://www.contributor-covenant.org/translations. 129 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to AzureTLS Client 2 | 3 | First off, thank you for considering contributing to this project! This document provides guidelines and instructions to help you contribute effectively. 4 | 5 | ## Code of Conduct 6 | 7 | By participating in this project, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md). 8 | 9 | ## How Can I Contribute? 10 | 11 | ### Reporting Bugs 12 | 13 | Before submitting a bug report: 14 | - Check the issue tracker to see if the bug has already been reported 15 | - Ensure the bug is related to the Go HTTP client and not a dependency 16 | 17 | When submitting a bug report: 18 | - Use a clear and descriptive title 19 | - Describe the exact steps to reproduce the bug 20 | - Provide specific examples (code snippets, configuration files) 21 | - Include relevant logs and error messages 22 | - Describe the expected behavior 23 | - Mention your environment details (Go version, OS, etc.) 24 | 25 | ### Suggesting Enhancements 26 | 27 | When suggesting an enhancement: 28 | - Use a clear and descriptive title 29 | - Provide a step-by-step description of the suggested enhancement 30 | - Explain why this enhancement would be useful to most users 31 | - Include code examples if applicable 32 | 33 | ### Pull Requests 34 | 35 | Follow these steps to submit a pull request: 36 | 37 | 1. Fork the repository 38 | 2. Create a new branch (`git checkout -b feature/your-feature-name`) 39 | 3. Make your changes 40 | 4. Run tests to ensure your changes don't break existing functionality 41 | 5. Commit your changes with clear commit messages that follow our commit message conventions 42 | 6. Push to the branch (`git push origin feature/your-feature-name`) 43 | 7. Open a pull request 44 | 45 | #### Pull Request Guidelines 46 | 47 | - Follow the standard Go code style and formatting guidelines 48 | - Write comprehensive comments for public functions, types, and methods 49 | - Include tests for new features or bug fixes 50 | - Update documentation to reflect any changes 51 | - Ensure all tests pass before submitting 52 | - Make sure your code lints without errors 53 | - Keep each PR focused on a single change to make review easier 54 | 55 | ## Development Setup 56 | 57 | 1. Install Go (version 1.24+) 58 | 2. Clone the repository 59 | 3. Install dependencies: `go mod download` 60 | 4. Run tests: `go test ./...` 61 | 62 | ## Coding Standards 63 | 64 | ### Go Code Style 65 | 66 | - Follow the [Effective Go](https://golang.org/doc/effective_go) guidelines 67 | - Use `gofmt` to format your code 68 | - Follow standard Go naming conventions 69 | - Document all exported functions, types, and methods 70 | 71 | ### Commit Message Conventions 72 | 73 | Structure your commit messages as follows: 74 | 75 | ``` 76 | : 77 | 78 | 79 | 80 |