Hey, I'd like to have some authentication options for mora API usage. I think it should be some out-of mongo, distributable authentication service, maybe Keystone (api docs) which is common choice in public and private clouds today as it's part of popular and strong OpenStack. I would like to hear other options and opinions about them, and maybe some voices against my word because Keystone was just a shot.

The parsing of the JSON body was being handled by go-restful, which uses the JSON decoder.UseNumber() method. This parses all numbers as strings instead of integers or floats, which makes it impossible to insert or update numeric values with mora. By handling the JSON parsing locally, we can skip UseNumber, so integers and floats remain as those native types.

See: https://github.com/emicklei/go-restful/blob/v1.1.3/request.go#L112-L114

resp.WriteHeader(status) in WriteStatus (response.go) is not required anymore as WriteEntity in go-restful support WriteHeaderAndEntity. So, we can use only resp.WriteHeaderAndEntity(status, r)

That creates "multiple response.WriteHeader calls" in logs.

I am trying to bring up an API for my mongoDB instance.

I currently have a user with read only rules that I can connect with so my mora.properties file looks like this:

#listener info is required
http.server.host=0.0.0.0
http.server.port=9123

mongo.db.uri=mongodb://user:pass@localhost:27017/mydb

I have also tried the following

#listener info is required
http.server.host=0.0.0.0
http.server.port=9123

#Auth 
mongod.mydb.databse=mydb
mongod.mydb.username=user
mongod.mydb.password=pass

mondod.mydb.host=localhost
mondod.mydb.port=27017

But when I try to do the following

$ curl http://localhost:9123/docs/mydb 
 {
   "success": false,
   "error": {
    "code": 401,
    "name": "unauthorized"
   }
  }

And the Mora instance logs:

2015/06/20 05:32:00 [mora] connecting to [db=mongodb://user:pass@localhost:27014/mydb] with timeout [0 seconds]
2015/06/20 05:32:00 [mora][error] unauthorized

Needless to say - I have checked my user authentication info several times - it is correct. The thing is - I have tried the exact same URI for mongoDB in another app (node.js mongodb-rest api) and it works, but for some reason Mora fails to authenticate.

Any ideas how to go around that?

This standardizes how complex BSON data types (like ObjectId, date fields, binary data, etc) get translated to JSON. It uses MongoDB's extended JSON specification: The heavy lifting is done by the mejson go library.

By treating the input queries as extended JSON, this allows for several types of queries that weren't previously possible. For example, it's now possible to query a date field like:

?query={"updated_at":{"$gt":{"$date":1426411642889}}}

Other special BSON types should be queryable in a similar fashion.

However, the output is backwards incompatible, since these various BSON field types now have a different output style. For example, what might have previously been returned as:

{
  "_id": "5505507a1c57d0372be0076c",
  "updated_at": "2015-03-15T09:27:22.889Z",
}

Is now returned as:

{
  "_id": {
    "$oid": "5505507a1c57d0372be0076c"
  },
  "updated_at": {
    "$date": 1426411642889
  }
}

String and numeric fields are not affected by this and will still be returned the same.

The change in package paths for the mgo library as part of this commit are for compatibility with the mejson library (which uses the gopkg.in url instead of the github.com address).

Note, this pull request also includes the commit to fix number handling from #31. That was included in this pull request too, since the number fixes are needed to properly handle the things like date parsing (since those are all treated as integers).

This adds support for calling SetMode on the session, which allows for choosing different read preferences (secondary, nearest, etc).

This also makes a small adjustment to point to the latest version of mgo's Dial documentation in the README's uri reference.

Is it by design or how can I reuse the TCP connection.

Looking at netstat this appears to be resulting in a new connection for every post resulting in a large number of concurrent connections being open.

What is the correct way to reuse connections in this case?

Each time I used another ip for http.server.host setting throws a binding exeception, here is the full log:

2016/10/24 18:24:55 [mora][info] loading configuration from [mora.properties]
[restful] 2016/10/24 18:24:55 log.go:30: [restful/swagger] listing is available at http://192.168.56.103:8181/apidocs.json
[restful] 2016/10/24 18:24:55 log.go:30: [restful/swagger] http://192.168.56.103:8181/apidocs/ is mapped to folder ./swagger-ui/dist
2016/10/24 18:24:55 [mora][info] ready to serve on http://192.168.56.103:8181
2016/10/24 18:24:55 listen tcp 192.168.56.103:8181: bind: cannot assign requested address

it works with localhost or empty string, whatever else fails.

When I'm creating a request to mora using Google Chrome I'm getting error:

xml: unsupported type: bson.M

Request:

GET /docs/lab/appg_test_env1/clients/5334dce9b734f91194000001 HTTP/1.1
Host: 127.0.0.1:4000
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8

Hey! Today I was writing a small HTTP API using MongoDB as a storage and I just thought, what if I could reuse mora? Tell me what do You think about it and check code which is my first attempt, I have decoupled and a little bit documented the code. It makes mora a little bit more reusable but we can go further.

It works with both /docs/alias/db/col (when creating) and /docs/alias/db/col/id (when updating or creating) now.

It fixed location of modified object in Content-Location header when document was updated with putDocument operation.

Request Url: http://127.0.0.1:8181/docs/local/use1/webservices/52519954b734f9036c000001 Request Method: PUT

Status Code: 201 ... Content-Location: /docs/local/use1/webservices/52519954b734f9036c000001/52519954b734f9036c000001

curl 'http://****?skip=1&limit=1'

response : { "success": true, "data": [] }

change limit =2 , the resoponse is ok .

looks like : limit=1， skip >= 1 ， empty limit = 1, skip = 0 ， ok limit > 1, ok

I find len(iter.docData)=0 and iter.err = "not found"

I was attempting to perform a PUT operation from Angular and kept getting rejected by CORS in Chrome. I checked the GET request I did prior to the PUT and noticed it went through fine (though no OPTIONS request was done for the GET). Upon attempting a PUT, the OPTIONS request goes through and returns a 200 as you'd expect with the Allow response header, but not the Access-Control-Allow-Origin or Access-Control-Expose-Headers headers. This caused Chrome to deny the request.

I've done some digging in mora and go-restful and it looks like the CrossOriginResourceSharing Filter method isn't being called on the OPTIONS request, though I'm not sure if that's by design and the OPTIONSFilter container func should be handling this instead. The CrossOriginResourceSharing filter method does get called successfully for the GET. I haven't checked to see if it gets called for DELETE or POST yet.

Also, for completeness sake, I haven't touched the cors setting in mora.properties. It was left in its default state of true.

Thanks for the great project!

I think its a good idea to validate the documents before we insert into the database, Using some kind of configuration includes a schema definition for every resource managed by the API.

Just like this link https://github.com/mongodb-labs/sleepy.mongoose/wiki/Database-Commands

When I tried to insert integer to mongodb, I found that mongodb shell is needed for this situation. Finding documents api of mora seems like support query operation only.

I wrote a json like {"a":10} into mongodb with mora, but the integer 10 becomes a double number 10.00 after writing. How to wrote a integer?

I'm trying to build mora in a new environment, but it's failing because it looks like the emicklei/goproperties repository has been deleted from github: https://github.com/emicklei/goproperties Was this intentional? I think I was building successfully last month when I thinks this repo still existed.

$ go get
# cd .; git clone https://github.com/emicklei/goproperties /tmp/gocode/src/github.com/emicklei/goproperties
Cloning into '/tmp/gocode/src/github.com/emicklei/goproperties'...
ERROR: Repository not found.
fatal: Could not read from remote repository.

I found the original upstream repo at dmotylev/goproperties, so I'm not sure if mora could be switched over to use that directly, or if there was relevant changes in your forked repo that are needed.

Thanks!