Customer (Fidelity #5651882)

"very interested to see if a new method could be introduced to the Apache community as a possible improvement. We have a real need to be able to encode a path that includes the JSESSIONID part, ie JSESSIONID=6736bcf34;foo=aabfa. We want to ask, whether such an improvement method (call it anything you want, encode_sticky() etc) to handle the additional sticky session path is possible."

1. Proposed title of this feature request
Apache HTTPD encode path

2. Who is the customer behind the request?
Account: Fidelity (Acct #5651882)

TAM customer: yes
SRM customer: no
Strategic: yes

3. What is the nature and description of the request?
Customer is working on custom module and requires additional API functionality to handle paths with inline session ID's
4. Why does the customer need this? (List the business requirements here)
Required in order to complete their custom module.
5. How would the customer like to achieve this? (List the functional requirements here)
API additions to Apache HTTPD.
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
N/A
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No.
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
No, customer has workaround but wanted to file this suggestion to help improve product.
9. Is the sales team involved in this request and do they have any additional input?
No, do not believe so.
10. List any affected packages or components.
httpd
11. Would the customer be able to assist in testing this functionality if implemented?
Yes.