Tag: HTTP

Categories
Knowledge Support Support exacqVision Client exacqVision Server exacqVision Webservice Categories

HTTP Response Code Reference

Code Description Definition Exacq Tips
Informational
100 Continue Server received request, client should continue.
101 Switching Protocols Response to upgrade header
102 Processing Server processing received request.
103 Early Hints Used with link header.
Allows browser to preload resources.
Successful
200 OK Standard response for successful request.
Meaning varies based on method (GET, POST, etc).
201 Created New resource successfully created.
Usually in response to PUT or POST request.
202 Accepted Request accepted but still in progress.
203 Non-Authoritative Info Data returned isn’t from the origin server.
Modified data from third-party.
204 No Content Request successful but there is no content.
205 Reset Content Request successful, server asked to reset doc.
206 Partial Content Server delivered part of the resource.
Used with range header.
207 Multi-Status Provides status of multiple resources with sub-requests.
208 Already Reported Members of element already reported.
226 IM Used Server completed GET request.
Redirection
300 Multiple Choices Request has more than one possible response.
User should choose one.
301 Moved Permanently Requested resource has permanently moved
to a new URL.
302 Found Requested resource temporarily moved to new URL.
303 See Other Server redirects user to requested resource
with GET request to another URL.
304 Not Modified Used for caching. Response unmodified so client can use cached version of resource.
307 Temporary Redirect Requested resource temporarily moved to new URL.
308 Permanent Redirect Requested resource permanently moved to new URL.
Client Error
400 Bad Request Server can’t or won’t process request due to client error.
401 Unauthorized User doesn’t have valid credentials to get requested
resource.		 Invalid username or password
403 Forbidden Client doesn’t have access rights to content.
Unlike 401, the server does know client’s identity.
404 Not Found Server can’t find requested resource. No redirection set. Request Not Found
The device didn’t understand the request.
May be caused by untested device or firmware.
405 Method Not Allowed Server supports request method, but target doesn’t.
406 Not Acceptable Server doesn’t find content satisfies criteria given by user.
407 Proxy Authentication Required Similar to 401, but proxy must authenticate to client.
408 Request Timeout Server times out because client didn’t issue request
in a timely manner.
409 Conflict Server can’t fulfill request due to conflict with resource.
410 Gone Requested content has been removed.
411 Length Required Server rejection becauce it requires defined
content-length header field.
412 Precondition Failed Client has precondition headers the server does not meet.
413 Payload Too Large Client request larger than server limits, so server
refuses to process request.
414 URI Too Long Requested URI is too long for server to process.
415 Unsupported Media Type Request uses media format unsupported by server.
416 Range Not Satisfiable Server can’t fulfill value in request’s range header.
417 Expectation Failed Server can’t meet requirements of expect header in request.
421 Misdirected Request Request made to server that can’t produce response.
422 Unprocessable Content Server unable to process request due to semantic errors.
423 Locked Requested resource method is locked to be inaccessible.
424 Failed Dependency Request failed because a previous request it is dependent on also failed.
425 Too Early Server is unwilling to process request that may be delayed.
426 Upgrade Required Server refuses request using current protocol version.
428 Precondition Required Server needs request to be conditional.
429 Too Many Requests User has sent too many requests within allotted time.
431 Request Header Fields Too Large Server can’t process request because headers are too large.
451 Unavailable For Legal Reasons Server can’t legally provide requested resource.
Server Error
500 Internal Server Error Server encountered unexpected error and cannot
complete the request.		 Device reporting an error.
The device has reported that it has encountered an error.
501 Not Implemented Server doesn’t recognize the request method.
502 Bad Gateway Server acts as a gateway and gets invalid response from inbound host.
503 Service Unavailable Server is unable to process request.
Often occurs if server is overloaded or down.		 Device Unavailable.
The device is currently unable to process this request.
504 Gateway Timeout Server acting as a gateway or proxy has timed out
waiting for response.
505 HTTP Version Unsupported Server doesn’t support the version of HTTP request.
506 Variant Also Negotiates Server has internal configuration error.
507 Insufficient Storage Server can’t process request because it doesn’t
have enough storage space.
508 Loop Detected Server detected infinite loop while processing request.
510 Not Extended Further extensions required for request.
511 Network Authentication Required Client needs to gain network access.

<br>

Categories
Knowledge Support Support exacqVision Webservice Products

exacqVision Web Server HTTP Policy “Redirect to HTTP” Broken

Description 

HTTP to HTTPS redirect implementation is broken and always supplies and internal IP address for the redirect, leading to any and all redirect from outside of the local network to fail.  

Product 

  • exacqVision Web Server 22.03

Steps to Reproduce 

  • Configure HTTPS on the web service, either external or ACME
  • Enable “Redirect to HTTPS” in the configuration
  • Attempt to connect to the web service via HTTP, e.g., `curl -v /login.web”>http://<url>/login.web`

Expected Results 

HTTP requests are redirected to HTTPS  

Actual Results 

Fails to connect  

Solution

Update exacqVision Web Service to 22.06 or above.

<br> 

See AESW-620 for additional information. 

<br>

Categories
Knowledge Support Support exacqVision Client

Green Lock and Gear Icons in the exacqVision Client

Description 

A green icon indicates a secure (HTTPS) connection is being used for either or both the configuration connection to the device and/or the video stream. 

Product 

exacqVision Client

Solution

The green lock and gear icons are used as a visual indicators of the connection protocol being used by the camera.  They can be found on the Cameras configuration page, the Add IP Cameras page and the Camera Recordings page. 

  • No Icon indicates standard connections are being used.
  • Green gear indicates that the device is secure, but the video stream is standard.
  • Green lock indicates that both the device and video stream are secure.
Categories
Knowledge Support Support exacqVision Server Categories Products

How to change web service ports

There are two ways to modify the ports used by the Web Service:

  1. Using the Web Service configuration interface
  2. Hand editing the configuration file

It is recommended to use the configuration interface, whenever possible. However, it is possible that you must hand edit the configuration in cases where the Web Service cannot start (for example, if there is a port conflict). This article provides instructions for both methods.

Important:  The structure and location of the Web Service config has changed over the life of the web service. Please pay close attention to the section headers in this article, as they indicate the versions to which particular instructions apply.

While various versions are mentioned in this article, it is recommend to keep your Web Service updated to the latest version to help prevent exposure to vulnerabilities and take advantage of the latest performance improvements.

<br>

Using the Web Service configuration UI

Versions 9.6 and above

Log into Web Service Configuration using your Web Service administrator account. Using the provided Web Service configuration interface navigate to Configuration > Ports.

Update the fields to change to your selected port number, then click ‘Apply’ to save your changes. The Web Service will need to restart to reflect your changes.

Versions 7.6 to 9.4

Web Service version 7.2 introduced Web Sockets for video streaming. Version 9.4 was the last version to feature Web Sockets, as it was replaced by other improvements.

When logging into Web Service Configuration, navigate to Configuration > Ports. Update the fields shown to your selected port numbers then click ‘Apply’ to save your changes. The Web Service will need to restart to reflect your changes.

Versions 7.2 to 7.6

Web Service version 7.2 introduced Web Sockets for video streaming. Version 9.4 was the last version to feature Web Sockets, as it was replaced by other improvements.

When logging into Web Service Configuration, navigate to Basic Service Configuration. You have the ability to update the Web Service Port and WebSocket Ports through the configuration page.

To change the HTTPS (SSL) or Secure WebSocket (SSL) ports requires manually editing the configuration file. See the section in this article titled ‘Manual Configuration‘ for more on these steps.

The Web Service will need to restart to reflect your changes.

Versions 7.0 and earlier

These versions are quite dated and as mentioned earlier, we recommend keeping your Web Services updated to help avoid vulnerabilities and take advantage of new features and performance enhancements.

<br>

Additional SSL Information

Note: Changing the SSL ports (https/wss) DOES NOT enable SSL. This merely allows you to easily modify those ports, but you still need to manually configure SSL support for both Apache and WebSockets. See the following article on configuring a certificate for HTTPS.

Firewall/Router Configuration

Note: Be sure to forward the new port in your router. Exacq Technical Support does not provide assistance with port forwarding, but see the following links if necessary:

<br>

Manual Configuration (hand editing the configuration)

The steps here will change depending on the type of port (HTTP vs. WebSockets) you wish to edit.

HTTP / HTTPS (Web Service verions 7.2 and above)

The first step to manual editing is to find the location of the config file where the port numbers are held. This depends on both the platform (operating system) and version of the Web Service you have installed.

Windows:

  • 9.0.x+ (both HTTP and HTTPS are in the same file):
    C:\ProgramData\Webservice\conf\wfe.json
  • 7.2.x – 8.8.x:
    • HTTP:
      C:\Program Files[(x86)]\exacqVision\WebService\Apache\conf\httpd.conf
    • HTTPS:
      C:\Program Files[(x86)]\exacqVision\WebService\Apache\conf\extra\httpd-ssl.conf

Linux:

  • 9.0.x+ (both HTTP and HTTPS are in the same file):
    /etc/webservice/wfe.json
  • 7.2.x – 8.8.x:
    • HTTP: /etc/evapache/httpd.conf
    • HTTPS: /etc/evapache/extra/httpd-ssl.conf

Determine where this file is for your install before continuing.

Once you have found the file, open it using your editor of choice (be sure to do so with administrative privileges) and perform either of the following depending on its name:

  • For httpd.conf (HTTP port) and httpd-ssl.conf (HTTPS port):
    1. Find the Listen directive in the file
      • For example, if the current port is 80, the line should read Listen 80
    2. Modify the port number as desired
    3. Save the file and restart Apache and the Web Service
  • For wfe.json:
    1. Find the webserver section
    2. For the HTTP port:
      • Find the listen key, nested one level within the webserver section
      • Modify the port number as desired
    3. For the HTTPS port:
      • Find the tls key, nested one level within the webserver section
      • Under the tls section, find the listen key one level below
      • Modify the port number as desired
    4. Save the file and restart the web service

<br>

Web Sockets (7.2.x – 9.4.x)

Both the standard and SSL WebSocket ports are changed from the Web Service ini/conf file. The location and name of this file depends on the platform (operating system) and web service version:

Windows:

  • 7.2.x – 9.4.x: C:\Program Files[(x86)]\exacqVision\WebService\WebService.ini

Linux:

  • 7.2.x – 8.8.x: /etc/webservice.conf
  • 9.0.x – 9.4.x: /etc/webservice/webservice.conf

Determine where this file is for your install before continuing.

Once you have found the file, open it using your editor of choice (be sure to do so with administrative privileges) and perform the following:

  1. Find the [Broker] section.
    This will only appear if it was entered manually before, or you configured it previously using the UI. So if you do not see it, and are configuring it for the first time, you may need to enter it by hand.
  2. The standard websocket port configuration is websocket_port = 8082, while the secure websocket port (wss) is ssl_port = 8083. Modify the port numbers as desired.
  3. As mentioned above, if these configuration settings are not already present, or the [Broker] section is missing, the defaults are being used. You may manually add the section/settings with desired values should this be the case. The resulting section of the file should appear similar to the below example, with your custom port numbers.
    [Broker]
    websocket_port = 8082
    ssl_port = 8083
  4. Save the file and restart the web service.

<br>