authorization-server-client - npm Package Compare versions

Comparing version 0.0.1 to 0.0.3

lib/client.js

@@ -55,3 +55,3 @@ (function() {
       body = null;
-      console.log("WE ARE HERE " + bodyBeforeJson);
+      
       if (bodyBeforeJson && bodyBeforeJson.length > 0) {
@@ -74,3 +74,3 @@ try {
       headers = {
-        'Content-Type': 'application/json'
+        'Accept': 'application/json'
       };
@@ -77,0 +77,0 @@ if (this.options.bearerToken) {

package.json

@@ -5,3 +5,3 @@ {
   "description": "Client to access an authorization server for oauth2 token validation in a distributed environment.",
-  "version": "0.0.1",
+  "version": "0.0.3",
   "main" : "lib/index.js",
@@ -8,0 +8,0 @@ "repository": {

README.md

@@ -7,3 +7,3 @@ ## About authorization-server-client
 resource server. In this case the resource server needs to be able to validate tokens against the
-authorization server. There are several ways to do this. One is to use public/private key encrypted long token that contain all the relevant information as part of the token. This requires
+authorization server. There are several ways to do this. One is to use public/private key encrypted long token that contains all the relevant information as part of the token. This requires
 sharing keys between authorization server and resource server. While fast this suffers 2 drawbacks: Long tokens and the necessity to work with very short lived tokens.
@@ -76,6 +76,6 @@
 
-* Change version in package.json
-* git tag -a v0.0.1 -m 'version 0.0.1'
+* git tag -a v0.0.3 -m 'version 0.0.3'
 * git push --tags
 * npm publish
+* update version in package.json and here
 
@@ -82,0 +82,0 @@ ## Contributing to authorization-server-client

No alert changes

Worsened metrics

Total package byte prevSize

14200

decreased by-0.68%

Lines of code

94

decreased by-1.05%

No dependency changes