You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-18Lines changed: 15 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,9 +53,8 @@ The KnownUser validation must be done on *all requests except requests for stati
53
53
So, if you add the KnownUser validation logic to a central place, then be sure that the Triggers only fire on page requests (including ajax requests) and not on e.g. image.
54
54
55
55
If we have the `integrationconfig.json` copied in the folder beside other knownuser files inside web application folder then
56
-
the following method is all that is needed to validate that a user has been through the queue:
56
+
the following method (using Django v.1.8) is all that is needed to validate that a user has been through the queue:
57
57
58
-
Example using Django v.1.8
59
58
```python
60
59
from django.http import HttpResponse
61
60
@@ -109,7 +108,7 @@ def index(request):
109
108
response.status_code =302
110
109
response["Location"] = requestUrlWithoutToken
111
110
112
-
return response
111
+
return response
113
112
114
113
except StandardError as stdErr:
115
114
# Log the Error
@@ -128,9 +127,8 @@ If your application server (maybe due to security reasons) is not allowed to do
128
127
3. Specify the configuration in code without using the Trigger/Action paradigm. In this case it is important *only to queue-up page requests* and not requests for resources or AJAX calls.
129
128
This can be done by adding custom filtering logic before caling the `KnownUser.resolveRequestByLocalEventConfig()` method.
130
129
131
-
The following is an example of how to specify the configuration in code:
130
+
The following is an example (using Django v.1.8) of how to specify the configuration in code:
132
131
133
-
Example using Django v.1.8
134
132
```python
135
133
from django.http import HttpResponse
136
134
@@ -149,16 +147,16 @@ def index(request):
149
147
customerId =""# Your Queue-it customer ID
150
148
secretKey =""# Your 72 char secret key as specified in Go Queue-it self-service platform
151
149
152
-
eventConfig = QueueEventConfig()
153
-
eventConfig.eventId =""# ID of the queue to use
154
-
eventConfig.queueDomain ="xxx.queue-it.net"#Domian name of the queue - usually in the format [CustomerId].queue-it.net
155
-
# eventConfig.cookieDomain = ".my-shop.com" #Optional - Domain name where the Queue-it session cookie should be saved
156
-
eventConfig.cookieValidityMinute =15#Optional - Validity of the Queue-it session cookie. Default is 10 minutes
157
-
eventConfig.extendCookieValidity = true #Optional - Should the Queue-it session cookie validity time be extended each time the validation runs? Default is true.
158
-
# eventConfig.culture = "da-DK" #Optional - Culture of the queue ticket layout in the format specified here: https://msdn.microsoft.com/en-us/library/ee825488(v=cs.20).aspx Default is to use what is specified on Event
159
-
# eventConfig.layoutName = "NameOfYourCustomLayout" #Optional - Name of the queue ticket layout - e.g. "Default layout by Queue-it". Default is to take what is specified on the Event
150
+
eventConfig = QueueEventConfig()
151
+
eventConfig.eventId =""# ID of the queue to use
152
+
eventConfig.queueDomain ="xxx.queue-it.net"#Domian name of the queue - usually in the format [CustomerId].queue-it.net
153
+
# eventConfig.cookieDomain = ".my-shop.com" #Optional - Domain name where the Queue-it session cookie should be saved
154
+
eventConfig.cookieValidityMinute =15#Optional - Validity of the Queue-it session cookie. Default is 10 minutes
155
+
eventConfig.extendCookieValidity = true #Optional - Should the Queue-it session cookie validity time be extended each time the validation runs? Default is true.
156
+
# eventConfig.culture = "da-DK" #Optional - Culture of the queue ticket layout in the format specified here: https://msdn.microsoft.com/en-us/library/ee825488(v=cs.20).aspx Default is to use what is specified on Event
157
+
# eventConfig.layoutName = "NameOfYourCustomLayout" #Optional - Name of the queue ticket layout - e.g. "Default layout by Queue-it". Default is to take what is specified on the Event
0 commit comments