Swagger-Requests schlagen fehl wegen alter Domain

Open Beginner friendly
#35 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
api

Research direction

Start with the Swagger index.html and review the URL-mapping change referenced in #34. Reproduce a browser request from https://nina.api.bund.dev/ and check why it still targets https://nina.api.proxy.bund.dev/api31/. Done when Swagger requests use https://warnung.bund.de and no longer depend on the inactive domain.

Written by the indexing model from the issue text.

Description

Die Requests, die per Browser von https://nina.api.bund.dev/ gestartet werden, landen alle bei https://nina.api.proxy.bund.dev/api31/, die Domain ist aber gar nicht mehr in Betrieb. Die aktuelle Domain ist warnung.bund.de.
Ich bin mir nicht ganz sicher, ob ich die Projektstruktur korrekt verstanden habe. In der index.html vom Swagger war ein URL-Mapping eingebaut, das habe ich in #34 entfernt. Damit müsste das direkt funktionieren.

Dominant language
Python
Stars
94
Forks
6
No merged PRs in 30d

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.

More from bundesAPI/nina-api

All issues in bundesAPI/nina-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.