Changes between Initial Version and Version 1 of Ticket #1199, comment 2
- Timestamp:
- 02/03/17 11:07:55 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1199, comment 2
initial v1 1 1 Putting the log more time for more clarification, 2 2 request is sent to 2 upstream, 3 to: 192.168.254.81:8080, 192.168.254.82:8080.(Request is sent to 2 upstream) 3 * to: 192.168.254.81:8080, 192.168.254.82:8080. 4 5 6 7 8 9 {{{ 10 11 eslog.2017-01-28.10.bz2:192.168.254.94 192.168.254.9 192.168.254.91 - [28/Jan/2017:10:46:03 +0000] "GET /vuconnect/billing?msisdn=21629xxxxxx&transactionID=null&billingCode=1341343074&parentbillingCode=1341343074&activityType=renewal&callbackURL=http://xxxxxx.com&authToken=null&activityResult=Success&requestTypeId=2&chargingMode=backend&itemId=26817&itemTypeId=4&languageId=1&subscriptionStatusId=4 HTTP/1.1" 200 490 "-" "Jakarta Commons-HttpClient?/3.1" "86.906" "-" "-" "-""-""-" to: 192.168.254.81:8080, 192.168.254.82:8080 "HE :: device_user_agent:" - "HE : : up_calling_line_id:" - "HE :: msisdn:" - "HE :: du_msisdn:" - "HE :: x_msisdn:" - "HE :: nokia_msisdn:" - "HE :: radius_1:" - "HE :: radius_2:" - "ARGS::" msisdn=216296XXXXX&transactionID=null&billingCode=1341343074&parentbillingCode=1341343074&activityType=renewal&callbackURL=http://xxxxxxx.com&authToken=null&activityResult=Success&requestTypeId=2&chargingMode=backend&itemId=26817&itemTypeId=4&languageId=1&subscriptionStatusId=4 12 13 14 }}} 15 16 4 17 Is this expected behavior? if it is, how can one make sure that request sent to 1 upstream will not go to next upstream in any case. This is required for out billing application to not process 2 requests in any case. 5 18