rusq / rusq/aklapi

Address API error [406]

Open
#32 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

upstream
Dominant language
HTML
Stars
25
Forks
6
PR merge metrics
No merged PRs in 30d

Description

Hi again,

Thanks for all your hard work keeping this project alive. Big shoutout to you guys who keep it going, love your work

I believe the program is broken again.

Over the last few days I've been getting this error message address {"error":"address API returned status code: 401"}
When I try using the 500 Queen Street example in the Readme, it seems to be returning HTML for the webpage

I wish I could help more but I don't know what I'm doing. Would it be possible to give me some headers on how I can assist for any future errors?

Thanks

Contributor guide

No contributing guide indexed for this repository

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 with the README's 500 Queen Street example and reproduce the address lookup, recording whether the service returns status 401 and HTML instead of the expected response. Trace the address API request and response handling, then verify the example succeeds or reports a useful diagnostic for the upstream failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.