-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a dynamic header in packager #53
Comments
Hi. You need to use headerFormat parameter to set up the header. If all of your header values are static, except length, you may set it like so: or you can add extra parameter mode (for the 000 and * thing): In the second case you need to add mode method that will return the header value in this section:
Looks like this heavy header is set by an upstream not by the client host. Looks really strange. |
I run the script as you proposed on option 1 this is what I have in verbose mode Your environment has been set up for using Node.js 12.16.0 (ia32) and npm. C:\Users\source\repos\iso-8583-socket-queue>node socketQueue.js --upstreamHost=46.182.6.101 --upstreamPort=9888 --listenHttpPort=8080 --headerFormat=length:n:4,data:an:9:206000000 --vv --logFile=log.txt I sent the following http |
For this case it takes an option to pass the raw part of client headers as JSON, but there is no such a feature implemented yet. |
Hi Thank you for your help I manage to fix the issue it was as yo just a matter of adding a routine in the header generator. This tools is really powerful thank you for bringing it to our hand. Please close this issue. |
Hi I am trying to configure a new header in order to connect with POWERCARD from HPS.
The ISO8583 format is the following :
[ Protocol identification] + [ PowerCARD header ] + [Type of message] + [Bit maps] + [Data fields]
so header look like this : [ Protocol identification] + [ PowerCARD header ] where
[ Protocol identification] = "ISO"
[ PowerCARD header ] =
Position Content
1-4 Number of characters in the message.
5 Product code associated with the message. Valid value: ‘2’ = POS
6-10 The version of the POS software.
11-13 In case of rejection of message for wrong format, this field must contain the number of the first erroneous element, otherwise it contains "000" If the TPE has messages waiting to be sent to the server, this field must contain "*".
a sample of header will be ISO0413211111000 where [ISO ] + [ 0413 + 2 + 11111 + 000 ]
please can you assist on the way to configure this so the POS sent the message to be routed on the upstream
The text was updated successfully, but these errors were encountered: