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

inconsistent "input" json field #362

Closed
ehsandeep opened this issue Aug 15, 2021 · 1 comment · Fixed by #366 or #370
Closed

inconsistent "input" json field #362

ehsandeep opened this issue Aug 15, 2021 · 1 comment · Fixed by #366 or #370
Assignees
@Mzack9999
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity.

Comments

@ehsandeep
Copy link
Member

ehsandeep commented Aug 15, 2021 •
edited
Loading

Describe the bug

echo thisisinvalid.com | httpx -silent -probe -json -ports 443 -timeout 1  | jq .

{
  "timestamp": "2021-08-15T19:25:56.326336+05:30",
  "url": "http://thisisinvalid.com:443",
  "input": "https://thisisinvalid.com:443",
  "error": "context deadline exceeded (Client.Timeout exceeded while awaiting headers)",
  "failed": true
}

Expected:- "input":"thisisinvalid.com"

Environment details

  • httpx -version : [INF] Current Version: v1.1.1
  • go version: go version go1.16.5 darwin/arm64
@ehsandeep ehsandeep added Status: Available No one has claimed responsibility for resolving this issue Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity. labels Aug 15, 2021
@Mzack9999 Mzack9999 self-assigned this Aug 16, 2021
@Mzack9999 Mzack9999 linked a pull request Aug 16, 2021 that will close this issue
Fixing inconsistent "input" field behavior #366
Merged
@ehsandeep
Copy link
Member Author

@nil0x42 this is now fixed in the dev version.

@ehsandeep ehsandeep added Status: Completed Nothing further to be done with this issue. Awaiting to be closed. and removed Status: Available No one has claimed responsibility for resolving this issue labels Aug 17, 2021
@ehsandeep ehsandeep linked a pull request Aug 17, 2021 that will close this issue
v1.1.2 Release preparation #370
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Mzack9999 Mzack9999

Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity.
Projects
None yet
Milestone
No milestone
2 participants
@ehsandeep @Mzack9999