Https request on failed

Https request on failed SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Https request on failed « Previous || Next »
Author Message
marc bazimon
Frequent Contributor
Username: Marc_orange

Post Number: 84
Registered: 01-2007
Posted on Thursday, September 05, 2019 - 10:38 am:   

Hi Support ,
on the MMSC.LOG , we have a lots of hhtps request on the 443 tcp port.
see below . our MMSC has no access to internet so the request are in failed status.
Do you know what does this request means and for what?
is it possible to avoid this ?


Line 195197: 2019-09-05 15:22:16,HTTPGET,x.x.0.165,,,ssl.google-analytics.com:443,FAILED
Line 195218: 2019-09-05 15:22:29,HTTPGET,x.x.0.165,,,mblapi.ssl2.duapps.com:443,FAILED
Line 195243: 2019-09-05 5:22:49,HTTPGET,x.x.0.165,,,www.googleapis.com:443,FAILED
Line 195249: 2019-09-05 15:22:51,HTTPGET,x.x.0.165,,,v1/scheme/app,FAILED
Line 195352: 2019-09-05 15:23:29,HTTPGET,x.x.0.165,,,www.googleapis.com:443,FAILED
Line 195384: 2019-09-05 15:23:52,HTTPGET,x.x.0.165,,,v1/scheme/app,FAILED
Line 195424: 2019-09-05 15:24:09,HTTPGET,x.x.2.118,,,www.googleapis.com:443,FAILED
Line 195430: 2019-09-05 15:24:10,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195431: 2019-09-05 15:24:10,HTTPGET,x.x.0.205,,,play.googleapis.com:443,FAILED
Line 195434: 2019-09-05 15:24:10,HTTPGET,x.x.0.205,,,play.googleapis.com:443,FAILED
Line 195435: 2019-09-05 15:24:11,HTTPGET,x.x.0.205,,,android.googleapis.com:443,FAILED
Line 195442: 2019-09-05 15:24:13,HTTPGET,x.x.2.118,,,ssl.google-analytics.com:443,FAILED
Line 195462: 2019-09-05 15:24:17,HTTPGET,x.x.0.205,,,clients4.google.com:443,FAILED
Line 195463: 2019-09-05 15:24:17,HTTPGET,x.x.0.205,,,clients4.google.com:443,FAILED
Line 195464: 2019-09-05 15:24:18,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195513: 2019-09-05 15:24:46,HTTPGET,x.x.0.165,,,play.googleapis.com:443,FAILED
Line 195516: 2019-09-05 15:24:50,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195517: 2019-09-05 15:24:50,HTTPGET,x.x.0.205,,,ssl.google-analytics.com:443,FAILED
Line 195522: 2019-09-05 15:24:53,HTTPGET,x.x.0.165,,,v1/scheme/app,FAILED
Line 195531: 2019-09-05 15:24:55,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195536: 2019-09-05 15:24:56,HTTPGET,x.x.0.165,,,ssl.google-analytics.com:443,FAILED
Line 195547: 2019-09-05 15:25:00,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195562: 2019-09-05 15:25:09,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195586: 2019-09-05 15:25:22,HTTPGET,x.x.2.118,,,graph.facebook.com:443,FAILED
Line 195595: 2019-09-05 15:25:26,HTTPGET,x.x.0.165,,,android.googleapis.com:443,FAILED
Line 195603: 2019-09-05 15:25:31,HTTPGET,x.x.2.118,,,play.googleapis.com:443,FAILED
Line 195606: 2019-09-05 15:25:31,HTTPGET,x.x.2.118,,,play.googleapis.com:443,FAILED
Line 195669: 2019-09-05 15:25:54,HTTPGET,x.x.0.165,,,v1/scheme/app,FAILED
Line 195696: 2019-09-05 15:26:09,HTTPGET,x.x.0.205,,,ssl.google-analytics.com:443,FAILED
Line 195697: 2019-09-05 15:26:09,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195711: 2019-09-05 15:26:14,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195725: 2019-09-05 15:26:20,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195737: 2019-09-05 15:26:25,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195748: 2019-09-05 15:26:31,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195753: 2019-09-05 15:26:37,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195766: 2019-09-05 15:26:43,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195777: 2019-09-05 15:26:48,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195779: 2019-09-05 15:26:53,HTTPGET,x.x.2.118,,,android.clients.google.com:443,FAILED
Line 195782: 2019-09-05 15:26:53,HTTPGET,x.x.2.118,,,www.googleapis.com:443,FAILED
Line 195785: 2019-09-05 15:26:54,HTTPGET,x.x.2.118,,,play.googleapis.com:443,FAILED
Line 195786: 2019-09-05 15:26:54,HTTPGET,x.x.2.118,,,android.googleapis.com:443,FAILED
Line 195787: 2019-09-05 15:26:55,HTTPGET,x.x.0.205,,,generate_204,FAILED
Line 195790: 2019-09-05 15:26:57,HTTPGET,x.x.0.165,,,v1/scheme/app,FAILED


On the debug the output is like this

14:07:23:488 [42] ThreadProcessConnection: Processing connection from x.x.0.205...
14:07:23:508 [42] ThreadProcessConnection: F:\MMSCDATA\api.parse.INI
14:07:23:508 [42] ThreadProcessConnection: File not found
14:07:23:508 [42] ThreadProcessConnection: F:\MMSCDATA\api.parse.com:443
14:07:23:508 [42] ThreadProcessConnection: HTTP/1.1 404 Not Found
Content-Length: 0
Connection: Keep-Alive


14:07:23:530 [37] ThreadProcessConnection: F:\MMSCDATA\ssl.google-analytics.INI
14:07:23:530 [37] ThreadProcessConnection: File not found
14:07:23:530 [37] ThreadProcessConnection: F:\MMSCDATA\ssl.google-analytics.com:443
14:07:23:530 [37] ThreadProcessConnection: HTTP/1.1 404 Not Found
Content-Length: 0
Connection: Keep-Alive


thanks beforehand for your help
Br
Marc
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 6043
Registered: 08-2008
Posted on Monday, September 09, 2019 - 10:22 pm:   

Hi Marc,

These are HTTP requests that are received on the MMSC port.

Even if the MMSC were connected to the internet, these requests would fail, because the MMSC will never function as a proxy.

I assume an app on the phones must be trying to use the MMSC as a proxy.


Des
NowSMS Support

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

Login Login / Register Logout Logout Search Last 30 Days Topics Topics