badsys
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 273
- Forks
- 391
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
File pages/web/domains/dns_dynhost/guide.en-ie.md doesn't explain any error(s) and etc. of the mentioned endpoint.
Right now I'm stuck pulling my hair out and trying to figure out what badsys response with HTTP status code of 200 mean. There isn't even a curl command example given.
The IP of my subdomain didn't change in the panel, dig still points to the old IP I've set manually in the panel and google returns no useful results.
Java code (okHttp library) that repoduces my issue:
public void updateDnsOkHttp(String name, String target) throws Exception {
log.info("Creating okHttp request");
OkHttpClient client = new OkHttpClient();
RequestBody body = RequestBody.create(null, new byte[0]);
final String url = baseUrl.replaceFirst("HOSTNAME", name + "." + configuration.BASE_DOMAIN).replaceFirst("IP", target);
Request request = new Request.Builder()
.url(url)
.post(body)
.header("Content-Length", "0")
.header("Authorization", Credentials.basic(configuration.OVH_USER, configuration.OVH_PASSWORD))
.build();
log.info("Executing request to: {}", url);
Response response = client.newCall(request).execute();
final String str = response.body().string();
log.info("Got response: {}", str);
final int code = response.code();
log.info("Got response code: {}", code);
if(code != 200) {
throw new Exception("Couldn't update DNS record, response code: " + code);
}
if(str.startsWith("badsys")) {
throw new Exception("Couldn't update DNS record");
}
}
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with pages/web/domains/dns_dynhost/guide.en-ie.md and inspect the documented endpoint and its response examples. Clarify what a badsys response with HTTP 200 means, explain the relevant errors and update behavior, and add a curl request example. Done means the guide covers the reported response and gives readers a reproducible request format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100