cancel
Showing results for 
Search instead for 
Did you mean: 
karthago
Level 9

SSL requests log file difference

Jump to solution

Hi,

we have two mwg7 appliances, one WG-5500B and one WG-5000B. Both using the same ruleset and log handler rules, and log settings are the same.

When i send the following request:

https://accounts.google.com/o/oauth2/postmessageRelay?parent=http%3A%2F%2Fwww.oe24.at

(example)

the first proxy writes to the log (from property Request.Header.FirstLine):

"GET https://accounts.google.com/o/oauth2/postmessageRelay?parent=http%3A%2F%2Fwww.oe24.at HTTP/1.1"

the second one:

"https://accounts.google.com/o/oauth2/postmessageRelay?parent=http%3A%2F%2Fwww.oe24.at HTTP/1.1"

Web Reporter (5.2.1.01) marks the second one as "invalid" and does not store it in the database.

Does anyone have the same problem? This causes approx. 1000 errors / 250.000 log lines.

Thanks

0 Kudos
1 Solution

Accepted Solutions
asabban
Level 17

Re: SSL requests log file difference

Jump to solution

Hello,

I slightly remember I have seen this issue before. I think it was a bug which should be fixed in the meantime, unfortunately I wasn't able to find the associated entry in out bug tracking system, so I cannot verify and/or provide details. In case you are running an older build of MWG (the tags state 7.1.6) my recommendation would be to perform an update to the latest version and see if the issue persists.

Best,

Andre

0 Kudos
2 Replies
asabban
Level 17

Re: SSL requests log file difference

Jump to solution

Hello,

I slightly remember I have seen this issue before. I think it was a bug which should be fixed in the meantime, unfortunately I wasn't able to find the associated entry in out bug tracking system, so I cannot verify and/or provide details. In case you are running an older build of MWG (the tags state 7.1.6) my recommendation would be to perform an update to the latest version and see if the issue persists.

Best,

Andre

0 Kudos
karthago
Level 9

Re: SSL requests log file difference

Jump to solution

Thanks Andre,

solved by updating to main release 7.3.2.3 (16052). Log lines containing status code 403 (blocked by MWG) now look like they should:

[...] 173.194.70.84 403 "GET https://accounts.google.com/o/oauth2/postmessageRelay?parent=http%3A%2F%2Fwww.tt.com HTTP/1.1" "Internet Services" [...]

0 Kudos