javascript - node.js / Https with express -

-

मैं node.js में https के साथ एक्सप्रेस का उपयोग करने का प्रयास करता हूं।

इस हिस्से के लिए यहां प्रासंगिक कोड: 

  var express = require ("express"); Var ऐप = एक्सप्रेस (); Var https = की आवश्यकता होती है ('https'); Var निजीकी = fs.readFileSync ('./sslcert / mykey.key', 'utf8'); Var प्रमाण पत्र = fs.readFileSync ('./sslcert / mssl.crt', 'utf8'); Var क्रेडेंशियल्स = {key: privateKey, cert: certificate}; Https.createServer (क्रेडेंशियल्स, ऐप) .listen (5008, फ़ंक्शन (रेस्क) {console.log ("सुनो:" + पोर्ट)});

कंसोल में, यह सुनो: 5008 प्रिंट करता है, लेकिन मुझे नहीं लगता कि मेरे सर्वर को कोई भी अनुरोध मिलता है, भले ही मैंने कुछ भेजा।

जब मैं एसएसएल एक्सटेंशन के बिना एक्सप्रेस का उपयोग करता हूं, तो सबकुछ ठीक काम करती है।

संपादित करें:

यहां जो कोड है जो 5008 पोर्ट के साथ ठीक काम करता है , लेकिन एसएसएल भाग के बिना: 

  var एक्सप्रेस = अपेक्षित ("एक्सप्रेस"); Var ऐप = एक्सप्रेस (); App.listen (5008, कार्य () {console.log ("" पोर्ट पर सुनना;;});

मैं क्या करूँ?

आपको निर्दिष्ट करना होगा < कोड> https: // , अन्यथा ब्राउजर / क्लाइंट कनेक्ट नहीं होने पर एसएसएल का उपयोग करने के लिए नहीं जानता है, भले ही पोर्ट क्या इस्तेमाल किया जाए (डिफ़ॉल्ट का 443 या अन्यथा)।


Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more