Updated number of seconds

Author: TBunkley

articles/spring-apps/how-to-configure-ingress.md

@@ -22,7 +22,7 @@ The Azure Spring Apps service uses an underlying ingress controller to handle ap
 | `ingress-read-timeout` | `proxy-read-timeout`     | 300           | \[1,1800\]        | The timeout in seconds for reading a response from a proxied server.     |
 | `ingress-send-timeout` | `proxy-send-timeout`     | 60            | \[1,1800\]        | The timeout in seconds for transmitting a request to the proxied server. |
 | `session-affinity`     | `affinity`               | None          | Session, None     | The type of the affinity that will make the request come to the same pod replica that was responding to the previous request. Set `session-affinity` to Cookie to enable session affinity. In the portal only, you must choose the enable session affinity box.    |
-| `session-max-age`      | `session-cookie-max-age` | 0             | \[0, 259200\]      | The time in seconds until the cookie expires, corresponding to the `Max-Age` cookie directive. If you set `session-max-age` to 0, the expiration period is equal to the browser session period. |
+| `session-max-age`      | `session-cookie-max-age` | 0             | \[0, 604800\]      | The time in seconds until the cookie expires, corresponding to the `Max-Age` cookie directive. If you set `session-max-age` to 0, the expiration period is equal to the browser session period. |
 | `backend-protocol`     | `backend-protocol`       | Default       | Default, GRPC     | Sets the backend protocol to indicate how NGINX should communicate with the backend service. Default means HTTP/HTTPS/WebSocket. The `backend-protocol` setting only applies to client-to-app traffic. For app-to-app traffic within the same service instance, choose any protocol for app-to-app traffic without modifying the `backend-protocol` setting. The protocol doesn't restrict your choice of protocol for app-to-app traffic within the same service instance.  |
 
 ## Prerequisites