We Keep Coding

Cannot read req.body in Next.js 13 middeware

In the code below I want to validate the request body with a schema from zod, currently, it will fail and catch. This is because req.body is returning a ReadableStream<Uint8Array> and not the object that it expects to parse.
export default async function middleware(req: NextRequest, res: NextResponse) {
const { pathname } = req.nextUrl;
if (pathname.startsWith('/api/user/create')) {
try {
createUserSchema.parse({
body: req.body,
params: req.nextUrl.searchParams,
});
return NextResponse.next();
} catch (error: any) {
console.log(req.body);
return NextResponse.json(
{ success: false, message: error },
{ status: 422, headers: { 'content-type': 'application/json' } }
);
}
}
return NextResponse.next();
}
this below is the output of the console.log(req.body);
<ref *1> ReadableStream {
_state: 'readable',
_reader: undefined,
_storedError: undefined,
_disturbed: false,
_readableStreamController: ReadableStreamDefaultController {
_controlledReadableStream: [Circular *1],
_queue: S {
_cursor: 0,
_size: 0,
_front: { _elements: [], _next: undefined },
_back: { _elements: [], _next: undefined }
},
_queueTotalSize: 0,
_started: false,
_closeRequested: false,
_pullAgain: false,
_pulling: false,
_strategySizeAlgorithm: [Function],
_strategyHWM: 1,
_pullAlgorithm: [Function],
_cancelAlgorithm: [Function]
}
}
I did some research and found that I need to run some kind of conversion method on this ReadableStream. The problem is that most of these include the Buffer module which cannot be run on the Edge and therefore cannot work in the middleware.ts. Is there perhaps a polyfill that I can use?
"next": "^13.0.7"
Node v16.17.0

Next.js middleware does not work the same as an Express middleware because it only runs on navigation and does not act as a catch-all for your API endpoints.
As per the documentation, you can only access cookies, access/modify request headers and perform redirects and rewrites using this feature.

You can use
const body = await req.json()

AWS-RunShellScript not invoked from Lambda function

I am using nodeJS 12.x lambda function to invoke certain commands on one of the EC2 instance. I have made sure that
SSM agent is installed on the EC2 instance
Proper roles are assigned to the lambda function, Policies are - AmazonEC2ReadOnlyAccess, AmazonSSMFullAccess, AWSLambdaExecute.
Below is the lambda code:
var AWS = require('aws-sdk');
const ssm = new AWS.SSM();
AWS.config.update({region:'ap-south-1'});
exports.handler = function(event, context) {
var ec2 = new AWS.EC2();
ec2.describeInstances(function(err, data) {
if(err) {
console.log(err, err.stack);
}
else {
let instance = data.Reservations[0].Instances[0].InstanceId;
console.log("\nInstance Id: ", instance);
ssm.sendCommand({
DocumentName: "AWS-RunShellScript",
InstanceIds: [ instance ],
TimeoutSeconds: 3600,
Parameters: {
commands: ['ifconfig']
}
}, function(err, data) {
if (err) {
console.log("\nError:", err);
} else {
console.log("\nSuccess: ", data);
}
context.done(null, 'Function Finished!');
})
}
});
};
When I invoke this function manually I am getting the status as pending. Below is the output log.
Response:
"Function Finished!"
Request ID:
"748b280a-4277-42a1-a0c3-************"
Function logs:
START RequestId: 748b280a-4277-42a1-a0c3-************ Version: $LATEST
2020-11-05T08:52:26.895Z 748b280a-4277-42a1-a0c3-************ INFO
Inside describe instances:
2020-11-05T08:52:26.952Z 748b280a-4277-42a1-a0c3-************ INFO
Instance Id: i-016f4673e082a829e
2020-11-05T08:52:27.237Z 748b280a-4277-42a1-a0c3-************ INFO
Success: {
Command: {
CommandId: '8b7a3b6d-4a7a-4259-9c82-************',
DocumentName: 'AWS-RunShellScript',
DocumentVersion: '',
Comment: '',
ExpiresAfter: 2020-11-05T10:52:27.220Z,
Parameters: { commands: [Array] },
InstanceIds: [ 'i-****************' ],
Targets: [],
RequestedDateTime: 2020-11-05T08:52:27.220Z,
Status: 'Pending',
StatusDetails: 'Pending',
OutputS3BucketName: '',
OutputS3KeyPrefix: '',
MaxConcurrency: '50',
MaxErrors: '0',
TargetCount: 1,
CompletedCount: 0,
ErrorCount: 0,
DeliveryTimedOutCount: 0,
ServiceRole: '',
NotificationConfig: {
NotificationArn: '',
NotificationEvents: [],
NotificationType: ''
},
CloudWatchOutputConfig: { CloudWatchLogGroupName: '', CloudWatchOutputEnabled: false },
TimeoutSeconds: 3600
}
}
END RequestId: 748b280a-4277-42a1-a0c3-************
REPORT RequestId: 748b280a-4277-42a1-a0c3-************ Duration: 677.90 ms Billed Duration: 700 ms Memory Size: 128 MB Max Memory Used: 96 MB
Why is the status not success? When I manually use 'RunCommand' it works properly.
What am I doing wrong?

The command status is showing as pending because, it is currently in pending. Once you execute the command it goes to from pending ----> Complete.
if you take the command ID (CommandId: '8b7a3b6d-4a7a-4259-9c82-************' in above case) and look into System Manager Run Command, by the time you try to search for it, it will show successful or failed

socket.io-client on server to connect to another server

So I have been working on setting up redundant servers without a single point of failure. I have been looking through a lot of methods and I have settled on using socket.io-client on each server to handle passing messages back and forth between the 2 servers for redundant data. However, no matter what I do, I cannot get the server to connect to the other server. I even scrapped my entire project, started a new one, using extremely simplistic code, and still cannot get the 2 to talk to each other. I have seen multiple questions like this on SO, but none of them have resolved my issue, so I decided to ask and give code samples of my ridiculously simple setup and see if anyone can see why it doesn't connect. I'm telling you, if I didn't already shave my head, I would be ripping my hair out by now. So, here is my simplistic code that doesn't work....
SERVER 1
"use strict";
const app = require('express')();
const http = require('http').Server(app);
const io = require('socket.io')(http);
const ioClient = require('socket.io-client');
app.get('/', (req, res) => {
res.sendFile(__dirname + '/index.html');
});
var client = ioClient('10.0.0.234:3000');
client.on('connect', () => {
console.log('connected to server');
});
io.on('connection', (socket) => {
socket.on('chat message', function(msg){
io.emit('chat message', msg);
});
});
http.listen(3000, () => {
console.log('listening on *:3000');
});
SERVER 2 -- exactly the same except for the line...
var client = ioClient('10.211.55.7:3000');
To point it at the other server. These are both on my local network, and both of them are running at the same time. I even put a client page on each server with a simple connection string, one to the server on that same machine, and one to the server on the other machine, like so...
CLIENT 1 (the 10.0.0.234 machine):
<script src="https://cdn.socket.io/socket.io-1.2.0.js"></script>
<script src="http://code.jquery.com/jquery-1.11.1.js"></script>
<script>
var socket = io("10.0.0.234:3000");
socket.on('connect', function() {
console.log('connected to main server');
})
$('form').submit(function(){
socket.emit('chat message', $('#m').val());
$('#m').val('');
return false;
});
socket.on('chat message', function(msg){
$('#messages').append($('<li>').text(msg));
});
</script>
CLIENT 2 (the 10.211.55.7 machine) - exactly the same except for the connection line which is...
var socket = io('10.211.55.7:3000');
Both of the clients work, and can connect to their servers. I even switched the IP addresses on the clients so that machine 10.0.0.234's client was using...
var socket = io('10.211.55.7:3000');
and it connected perfectly. So each client can connect to either server, and it works perfectly, but no matter what I do, I cannot get the server to ever log the 'connected to server' part.
Seriously, am I losing my mind here? IS there some random bug in socket.io-client that won't allow a server to connect to another server, even if it is running the socket.io as a client? I am so very...very... confused, annoyed, fed up, beat up... and all the other adjectives you can think of.
Just in case anyone needs it, here is my package.json file that I am running on both servers...
PACKAGE.JSON...
{
"name": "simple-socket",
"version": "0.0.1",
"description": "socket server to socket server test",
"dependencies": {
"express": "4.10.2",
"socket.io": "1.2.0",
"socket.io-client": "^1.4.5"
}
}
I know there are other ways of handling redundant backups within node.js,the actual server is much more complex running sticky-session, cluster, redis, socket.io-redis, and others. I just created a simplistic example (actually just kind of used the socket.io chat example as a base) to try to get both servers to talk to each other. No matter what though, it never actually connects to the other server. Yet, somehow both clients can connect to either server, it is just the server will not connect to the other server. Thank you for all the help, and I apologize for the novel here, I am just trying to give all the information I possibly can. Nothing more annoying than trying to help someone who won't give you anything in terms of information, and won't even do some basic research.
Here is a console.log(client); right after the "var client = ioClient('10.0.0.234:3000');
Socket {
io:
Manager {
nsps: { '/': [Circular] },
subs: [ [Object], [Object], [Object] ],
opts:
{ path: '/socket.io',
hostname: '10.0.0.234',
secure: false,
port: '3333' },
_reconnection: true,
_reconnectionAttempts: Infinity,
_reconnectionDelay: 1000,
_reconnectionDelayMax: 5000,
_randomizationFactor: 0.5,
backoff: Backoff { ms: 1000, max: 5000, factor: 2, jitter: 0.5, attempts: 0 },
_timeout: 20000,
readyState: 'opening',
uri: 'http://10.0.0.234:3333',
connecting: [ [Circular] ],
lastPing: null,
encoding: false,
packetBuffer: [],
encoder: Encoder {},
decoder: Decoder { reconstructor: null },
autoConnect: true,
engine:
Socket {
secure: false,
agent: false,
hostname: '10.0.0.234',
port: '3333',
query: {},
upgrade: true,
path: '/socket.io/',
forceJSONP: false,
jsonp: true,
forceBase64: false,
enablesXDR: false,
timestampParam: 't',
timestampRequests: undefined,
transports: [Object],
readyState: 'opening',
writeBuffer: [],
policyPort: 843,
rememberUpgrade: false,
binaryType: null,
onlyBinaryUpgrades: undefined,
perMessageDeflate: [Object],
pfx: null,
key: null,
passphrase: null,
cert: null,
ca: null,
ciphers: null,
rejectUnauthorized: null,
transport: [Object],
_callbacks: [Object] },
skipReconnect: false,
_callbacks: { '$open': [Object], '$packet': [Object], '$close': [Object] } },
nsp: '/',
json: [Circular],
ids: 0,
acks: {},
receiveBuffer: [],
sendBuffer: [],
connected: false,
disconnected: true,
subs:
[ { destroy: [Function] },
{ destroy: [Function] },
{ destroy: [Function] } ],
_callbacks:
{ '$connecting': [ [Function: onConnecting] ],
'$connect': [ [Function] ] } }

Websocket SSL connection

I am trying to test a secure websocket but I'm having trouble. Here is my test:
var WebSocket = require('ws');
describe('testing Web Socket', function() {
it('should do stuff', function(done) {
var ws = new WebSocket('wss://localhost:15449/', {
protocolVersion: 8,
origin: 'https://localhost:15449'
});
ws.on('open', function() {
console.log('open!!!');
done();
});
console.log(ws);
});
});
Here's the log of "ws" after it's created:
{ domain: null,
_events: { open: [Function] },
_maxListeners: undefined,
_socket: null,
_ultron: null,
_closeReceived: false,
bytesReceived: 0,
readyState: 0,
supports: { binary: true },
extensions: {},
_isServer: false,
url: 'wss://localhost:15449/',
protocolVersion: 8 }
I don't get a log back from open. I am running the project locally and when I use the Chrome Advanced Rest Client tool I am able to connect just fine.
Am I missing something? Please help.
Edit:
I added ws.on('error') and it logged out { [Error: self signed certificate] code: 'DEPTH_ZERO_SELF_SIGNED_CERT' }
I've also tried following this code but get the same error.

The https module is rejecting your self-signed cert (as one would hope). You can force it to stop checking by passing a rejectUnauthorized: false option (which WebSocket will pass down to https):
var ws = new WebSocket('wss://localhost:15449/', {
protocolVersion: 8,
origin: 'https://localhost:15449',
rejectUnauthorized: false
});

Querying for objects. "q" query does not work

With the Javascript API, I'm doing this:
client.search({
index:'530d8aa855df0c2d269a5a58',
type:'532a2b28495c533e5eaeb020',
q:'slide'
},function (error,response){
if(error){
console.log(error);
}
if(response){
console.log(response);
}
});
I want to search any document containing the word 'slide'.
The query returns no hits.
However, if I type this:
http://server:9200/530d8aa855df0c2d269a5a58/532a2b28495c533e5eaeb020/_search?pretty=true
Into a browser, I get hits.
What am I doing wrong?
More information:
The javascript query returns this:
Elasticsearch DEBUG: 2014-05-20T00:19:04Z
starting request { method: 'POST',
path: '/530d8aa855df0c2d269a5a58/532a2b28495c533e5eaeb020/_search',
query: { q: 'slide' } }
Elasticsearch TRACE: 2014-05-20T00:19:04Z
-> POST http:/server:9200/530d8aa855df0c2d269a5a58/532a2b28495c533e5eae
b020/_search?q=slide
<- 200
{
"took": 3,
"timed_out": false,
"_shards": {
"total": 5,
"successful": 5,
"failed": 0
},
"hits": {
"total": 0,
"max_score": null,
"hits": []
}
}
Elasticsearch INFO: 2014-05-20T00:19:04Z
Request complete
{ took: 3,
timed_out: false,
_shards: { total: 5, successful: 5, failed: 0 },
hits: { total: 0, max_score: null, hits: [] } }
I'm indexing my information like this:
client.index({
index:data2.name,
type:data2.files[i].author,
id:data2.files[i]._id.toString(),
body:data2.files[i]
},function(err,resp){
if(err){console.log(err)};
if(resp){console.log(resp)};
});
Edit:
The entirety of my node.js app is this:
var elasticsearch = require('elasticsearch');
var client = new elasticsearch.Client({
host: 'server:9200',
log:'trace'
});
client.search({
q:'slide'
},function (error,response){
if(error){
console.log(error);
}
if(response){
console.log(response);
}
});
With the exception that server is replaced with a real ip address.
My node app is running locally, and it's connecting to an EC2 instance which has ports 80, 443, 9200, and 9300 open.
EDIT2:
I changed my app to this:
client.search({
},function (error,response){
if(error){
console.log(error);
}
if(response){
console.log(response);
}
});
And I got everything. However, how do I specify a query, and yet have it work?
EDIT3:
The node.js elasticsearch module I'm using is v2.1.6
The API I'm looking at is for something called v1.1

I was able to run queries by replacing
q:'slide'
With
query:'slide'
So either the version of elasticsearch that I have doesn't match the documentation, or the documentation is wrong.