mirror of
https://github.com/node-red/node-red.git
synced 2025-03-01 10:36:34 +00:00
Change types from text/x-red to text/html in node html files
This commit is contained in:
@@ -14,6 +14,6 @@
|
||||
limitations under the License.
|
||||
-->
|
||||
|
||||
<script type="text/x-red" data-help-name="tls-config">
|
||||
<script type="text/html" data-help-name="tls-config">
|
||||
<p>Configuration options for TLS connections.</p>
|
||||
</script>
|
||||
|
@@ -14,7 +14,7 @@
|
||||
limitations under the License.
|
||||
-->
|
||||
|
||||
<script type="text/x-red" data-help-name="http proxy">
|
||||
<script type="text/html" data-help-name="http proxy">
|
||||
<p>Configuration options for HTTP proxy.</p>
|
||||
|
||||
<h3>Details</h3>
|
||||
|
@@ -11,7 +11,7 @@
|
||||
limitations under the License.
|
||||
-->
|
||||
|
||||
<script type="text/x-red" data-help-name="mqtt in">
|
||||
<script type="text/html" data-help-name="mqtt in">
|
||||
<p>Connects to a MQTT broker and subscribes to messages from the specified topic.</p>
|
||||
<h3>Outputs</h3>
|
||||
<dl class="message-properties">
|
||||
@@ -31,7 +31,7 @@
|
||||
<p>Several MQTT nodes (in or out) can share the same broker connection if required.</p>
|
||||
</script>
|
||||
|
||||
<script type="text/x-red" data-help-name="mqtt out">
|
||||
<script type="text/html" data-help-name="mqtt out">
|
||||
<p>Connects to a MQTT broker and publishes messages.</p>
|
||||
<h3>Inputs</h3>
|
||||
<dl class="message-properties">
|
||||
@@ -60,7 +60,7 @@
|
||||
<p>Several MQTT nodes (in or out) can share the same broker connection if required.</p>
|
||||
</script>
|
||||
|
||||
<script type="text/x-red" data-help-name="mqtt-broker">
|
||||
<script type="text/html" data-help-name="mqtt-broker">
|
||||
<p>Configuration for a connection to an MQTT broker.</p>
|
||||
<p>This configuration will create a single connection to the broker which can
|
||||
then be reused by <code>MQTT In</code> and <code>MQTT Out</code> nodes.</p>
|
||||
|
@@ -14,7 +14,7 @@
|
||||
limitations under the License.
|
||||
-->
|
||||
|
||||
<script type="text/x-red" data-help-name="http in">
|
||||
<script type="text/html" data-help-name="http in">
|
||||
<p>Creates an HTTP end-point for creating web services.</p>
|
||||
<h3>Outputs</h3>
|
||||
<dl class="message-properties">
|
||||
@@ -54,7 +54,7 @@
|
||||
must include an HTTP Response node to complete the request.</p>
|
||||
</script>
|
||||
|
||||
<script type="text/x-red" data-help-name="http response">
|
||||
<script type="text/html" data-help-name="http response">
|
||||
<p>Sends responses back to requests received from an HTTP Input node.</p>
|
||||
|
||||
<h3>Inputs</h3>
|
||||
|
@@ -14,7 +14,7 @@
|
||||
limitations under the License.
|
||||
-->
|
||||
|
||||
<script type="text/x-red" data-help-name="http request">
|
||||
<script type="text/html" data-help-name="http request">
|
||||
<p>Sends HTTP requests and returns the response.</p>
|
||||
|
||||
<h3>Inputs</h3>
|
||||
|
@@ -14,14 +14,14 @@
|
||||
limitations under the License.
|
||||
-->
|
||||
|
||||
<script type="text/x-red" data-help-name="websocket in">
|
||||
<script type="text/html" data-help-name="websocket in">
|
||||
<p>WebSocket input node.</p>
|
||||
<p>By default, the data received from the WebSocket will be in <code>msg.payload</code>.
|
||||
The socket can be configured to expect a properly formed JSON string, in which
|
||||
case it will parse the JSON and send on the resulting object as the entire message.</p>
|
||||
</script>
|
||||
|
||||
<script type="text/x-red" data-help-name="websocket out">
|
||||
<script type="text/html" data-help-name="websocket out">
|
||||
<p>WebSocket out node.</p>
|
||||
<p>By default, <code>msg.payload</code> will be sent over the WebSocket. The socket
|
||||
can be configured to encode the entire <code>msg</code> object as a JSON string and send that
|
||||
@@ -34,10 +34,10 @@
|
||||
should delete the <code>msg._session</code> property within the flow.</p>
|
||||
</script>
|
||||
|
||||
<script type="text/x-red" data-help-name="websocket-listener">
|
||||
<script type="text/html" data-help-name="websocket-listener">
|
||||
<p>This configuration node creates a WebSocket Server endpoint using the specified path.</p>
|
||||
</script>
|
||||
|
||||
<script type="text/x-red" data-help-name="websocket-client">
|
||||
<script type="text/html" data-help-name="websocket-client">
|
||||
<p>This configuration node connects a WebSocket client to the specified URL.</p>
|
||||
</script>
|
||||
|
@@ -14,14 +14,14 @@
|
||||
limitations under the License.
|
||||
-->
|
||||
|
||||
<script type="text/x-red" data-help-name="tcp in">
|
||||
<script type="text/html" data-help-name="tcp in">
|
||||
<p>Provides a choice of TCP inputs. Can either connect to a remote TCP port,
|
||||
or accept incoming connections.</p>
|
||||
<p><b>Note: </b>On some systems you may need root or administrator access
|
||||
to access ports below 1024.</p>
|
||||
</script>
|
||||
|
||||
<script type="text/x-red" data-help-name="tcp out">
|
||||
<script type="text/html" data-help-name="tcp out">
|
||||
<p>Provides a choice of TCP outputs. Can either connect to a remote TCP port,
|
||||
accept incoming connections, or reply to messages received from a TCP In node.</p>
|
||||
<p>Only the <code>msg.payload</code> is sent.</p>
|
||||
@@ -34,7 +34,7 @@
|
||||
to access ports below 1024.</p>
|
||||
</script>
|
||||
|
||||
<script type="text/x-red" data-help-name="tcp request">
|
||||
<script type="text/html" data-help-name="tcp request">
|
||||
<p>A simple TCP request node - sends the <code>msg.payload</code> to a server tcp port and expects a response.</p>
|
||||
<p>Connects, sends the "request", and reads the "response". It can either count a number of
|
||||
returned characters into a fixed buffer, match a specified character before returning,
|
||||
|
@@ -14,7 +14,7 @@
|
||||
limitations under the License.
|
||||
-->
|
||||
|
||||
<script type="text/x-red" data-help-name="udp in">
|
||||
<script type="text/html" data-help-name="udp in">
|
||||
<p>A UDP input node, that produces a <code>msg.payload</code> containing a
|
||||
Buffer, string, or base64 encoded string. Supports multicast.</p>
|
||||
<p>It also provides <code>msg.ip</code> and <code>msg.port</code> set to the
|
||||
@@ -23,7 +23,7 @@
|
||||
ports below 1024 and/or broadcast.</p>
|
||||
</script>
|
||||
|
||||
<script type="text/x-red" data-help-name="udp out">
|
||||
<script type="text/html" data-help-name="udp out">
|
||||
<p>This node sends <code>msg.payload</code> to the designated UDP host and port. Supports multicast.</p>
|
||||
<p>You may also use <code>msg.ip</code> and <code>msg.port</code> to set the destination values, but the statically configured values have precedence.</p>
|
||||
<p>If you select broadcast either set the address to the local broadcast ip address, or maybe try 255.255.255.255, which is the global broadcast address.</p>
|
||||
|
Reference in New Issue
Block a user