TLS renegotiation

Open
#223 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go

Research direction

No source file, test, or entry point is identified. Start by reproducing the image request against the linked imageproxy setup and investigate how the tool configures TLS for outbound HTTPS requests. Done means establishing whether imageproxy can resolve the renegotiation error and documenting the required change or configuration.

Written by the indexing model from the issue text.

Description

On some images I receive the following error, for example trying to serve this through imageproxy;
Get https://www.theaudiodb.com/images/media/album/thumb/parels-voor-de-zwijnen-51694d7c2afc3.jpg: local error: tls: no renegotiation

Is this a problem on my end (misconfiguration)? It seems like, from what I've read about the subject, it's a setting within this tool? See for example this stackoverflow thread;
https://stackoverflow.com/questions/57420833/tls-no-renegotiation-error-on-http-request

Any help resolving this would be awesome!

Dominant language
Go
Stars
4k
Forks
513
PR merge metrics
No merged PRs in 30d

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 willnorris/imageproxy

All issues in willnorris/imageproxy

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.