TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace: • sync_suite • simplemanagement • veeam • pattern_matching • tmss10scripts • add_remove_flags_by_last_read • function_send • function_scanning_in • paths • function_reconciliation
cli:http_proxy

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
cli:http_proxy [2017/06/07 23:06] – Gerard Nicolcli:http_proxy [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 2: Line 2:
  
 TapeTrack Command Line programs can be configured to send requests via a HTTP Proxy through the use of the [[variable:tmssserverproxy|TMSSSERVERPROXY]] environmental variable. TapeTrack Command Line programs can be configured to send requests via a HTTP Proxy through the use of the [[variable:tmssserverproxy|TMSSSERVERPROXY]] environmental variable.
 +
 +Support for HTTP tunneling includes support for basic HTTP authentication. Support for Kerberos authentication is not currently supported.
  
 <note tip>When troubleshooting HTTP Proxy connections, you should consider using the [[variable:tmssapilogdir|TMSSAPLILOGDIR]] environmental variable.</note> <note tip>When troubleshooting HTTP Proxy connections, you should consider using the [[variable:tmssapilogdir|TMSSAPLILOGDIR]] environmental variable.</note>
  
 <code> <code>
-C:\Users\gnicol\Desktop>set TMSSSERVERPROXY=192.168.1.8:3128+C:\Users\jsmith\Desktop>set TMSSSERVERPROXY=192.168.1.8:3128
  
-C:\Users\gnicol\Desktop>set TMSSAPILOGDIR=C:\Users\gnicol.GAZILLABYTE\Desktop+C:\Users\jsmith\Desktop>set TMSSAPILOGDIR=C:\Users\jsmith.GAZILLABYTE\Desktop
  
-C:\Users\gnicol\Desktop>TMSS10Ping -P 443 databank.tapetrack.com+C:\Users\jsmith\Desktop>TMSS10Ping -P 443 databank.tapetrack.com
 44 bytes from 192.168.1.8: seq=1 time=371.00 ms 44 bytes from 192.168.1.8: seq=1 time=371.00 ms
 44 bytes from 192.168.1.8: seq=2 time=308.00 ms 44 bytes from 192.168.1.8: seq=2 time=308.00 ms
Line 31: Line 33:
 19:12:28: TMSS10API_ConnectViaProxy: Connection to server (192.168.1.8) successful 19:12:28: TMSS10API_ConnectViaProxy: Connection to server (192.168.1.8) successful
 19:12:28: TMSS10API_Send: Function(Ping) Length(0) Flags(0) OptArgs(0) 19:12:28: TMSS10API_Send: Function(Ping) Length(0) Flags(0) OptArgs(0)
-19:12:29: TMSS10API_Send: RC(Request OK) Feedback(0) MiliSecs(0) Avail(0) Count(0) Length(0)+19:12:29: TMSS10API_Send: RC(Request OK) Feedback(0) MilliSecs(0) Avail(0) Count(0) Length(0)
 19:12:29: TMSS10API_Send: Function(Ping) Length(0) Flags(0) OptArgs(0) 19:12:29: TMSS10API_Send: Function(Ping) Length(0) Flags(0) OptArgs(0)
-19:12:29: TMSS10API_Send: RC(Request OK) Feedback(0) MiliSecs(0) Avail(0) Count(0) Length(0)+19:12:29: TMSS10API_Send: RC(Request OK) Feedback(0) MilliSecs(0) Avail(0) Count(0) Length(0)
 19:12:29: TMSS10API_Send: Function(Ping) Length(0) Flags(0) OptArgs(0) 19:12:29: TMSS10API_Send: Function(Ping) Length(0) Flags(0) OptArgs(0)
-19:12:29: TMSS10API_Send: RC(Request OK) Feedback(0) MiliSecs(0) Avail(0) Count(0) Length(0)+19:12:29: TMSS10API_Send: RC(Request OK) Feedback(0) MilliSecs(0) Avail(0) Count(0) Length(0)
 19:12:29: TMSS10API_Send: Function(Ping) Length(0) Flags(0) OptArgs(0) 19:12:29: TMSS10API_Send: Function(Ping) Length(0) Flags(0) OptArgs(0)
-19:12:29: TMSS10API_Send: RC(Request OK) Feedback(0) MiliSecs(0) Avail(0) Count(0) Length(0)+19:12:29: TMSS10API_Send: RC(Request OK) Feedback(0) MilliSecs(0) Avail(0) Count(0) Length(0)
 19:12:29: TMSS10API_Term 19:12:29: TMSS10API_Term
 </code> </code>
  
cli/http_proxy.1496876785.txt.gz · Last modified: 2025/01/21 22:07 (external edit)