Closed ksanislo closed 8 years ago
That's alright. Still, thank you a ton for making this possible in the first place, you rock!
Closing this with the release of https://github.com/Wolvan/Homebr3w/releases/tag/v1.1.0, if you're alright with that. Thanks a lot for your help, couldn't have done that without you.
No problem at all. It all looks damn good from the server side, nice work yourself!
I'll keep the proxy scripts on for a while longer so 1.0.0 still works. Most of the requests should have a proper header set except the getcia, I hope you don't mind.
It's no problem at all. I'm still waiting for an FBI release with headers, then I'll have to wait for everyone to upgrade off that as well before I can start rejecting headerless connections. Really, I just need to be able to tell what is what on the server side when there's problems, and your proxy stuff all comes from one IP so it's pretty easy to tell what it is. On Sat, Jul 16, 2016 at 3:26 PM Wolvan notifications@github.com wrote:
I'll keep the proxy scripts on for a while longer so 1.0.0 still works. Most of the requests should have a proper header set except the getcia, I hope you don't mind.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Wolvan/Homebr3w/issues/1#issuecomment-233154247, or mute the thread https://github.com/notifications/unsubscribe-auth/AECriOMrPriXOOJ2ShQFkokqP8Ue5RuZks5qWVqvgaJpZM4JKlhr .
Fair enough, thanks for understanding. It was a pleasure being able to work with you!
Yeah, the same goes for working with you. I've still got some plans to fix keep-alive connections in ctrulib, so I'll get the changes added to lpp and let you know when I do. Pulling all those images will be way faster if the 3ds doesn't build and break down a tcp connection to do each of them. So you haven't heard the last of me quite yet. ;)
I shall await this day then.
Please make sure that all access you're directing toward api.titledb.com has an HTTP User-Agent header set. It needs to contain at a minimum the application name and version number that is making the request, something like
User-Agent: Homebr3w/1.0.0
Or more thoroughly, since you may be redirected to a host that won't return results unless it thinks you're a web browser:
User-Agent: Mozilla/5.0 (Nintendo 3DS; Mobile; rv:10.0) Gecko/20100101 Homebr3w/1.0.0
If you don't set a User-Agent header, you're going to be blocked out of access to the API backend until it is added. Right now I'm still allowing unidentified clients since FBI wasn't set up correctly, but the next version has already been patched, and I'll begin blocking unknown clients sometime shortly after it's public release.