New answers tagged

3

To answer your second question - no, it isn't feasible to automatically scan for webmail providers. A web mail provider is simply a web application. It doesn't follow any specific standard or expose a specific interface. It's just a web site with functionality. It can be mostly server-side or have client-side elements. It can be written in PHP, or ...


0

OAuth2 defines a grant flow called client credentials grant. This allows an application to authenticate as itself and acquire an access token from the authorization server. It requires the client to register itself (get a client id) and create a client secret. It seems that the API you're using does support this.


1

You implement a form of microservice architecture - each of the 25 sites has a 'front end' (to them) that is a back end to your website. You make requests to each of these which make the appropriate request to the sites. Its up to you how to aggregate the results you get back, whether to take them as they come, or to hold them and process them into a single ...


1

Rather than centralising the date overnight, why not use a user interface, which naturally shows the progress on each of the sites being searched. https://iwantmyname.com/?domain=somedomain is a good example interface for domain name search. You would basically set up a user interface with 25 rows, which contain the name of each of your databases. The ...


-1

Returning the HTTP response header is the good practice because the the consumer can read the header without parsing your response.


4

Short answer is that 404 is the correct way to go. Long answer is that the HTTP status codes relate to state transfer between the client and the server, and are NOT designed to indicate any issue with the server's database data model. The server is for the most part a black box to the client when it comes to the HTTP layer. To clarify my answer I'm going ...


3

I would go with something like the following. A path parameter gives you a unique uri for a resource like /userinfo/user/123 Where 123 is the user id. Here I would return 404 as the specified resource did not exist. You could also validate the id and send back a 400 (Bad request) if the user id that was sent does not match a given pattern. If we instead ...


0

Where I work we use the 404 status code only as a response when an endpoint could not be found, that is when the route did not exist. If you successfully hit the server but it couldn't respond with 200, because the input data was either malformed or no match could be found against it, we throw 400 bad request code instead. The error message from our server ...


9

The user is the resource and if it's not there you return 404 resource not found. The URI is the representation of the entity. That's the whole point. 404 means the server was contacted and they couldn't find a resource and it returns 404. If you are getting a server side error, there's a whole range of errors for that in the 500 range and that is what ...


1

Also, don't be afraid tot tell me it's a silly idea. It's a silly idea :P And here's why: Data caps. The primary hog when it comes to data are things that happen in the background without any user's consent. You wouldn't want to be leeching off a person's data. Battery and heat. Of course, processing takes up resources and resources doesn't come free, ...



Top 50 recent answers are included