Custom WAP Gateway

This WAP gateway will be required to carry out a specific set of initial requirements, but should be built in such a way as the functionality may be expanded and modified easily. Below is a base set of requirements that the application needs to meet, including the use of the starting base and programming language. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows: 1. The gateway will proxy requests to a variety of different web sites, both internal and external, and will listen to proxy requests on port 80. 2. The gateway will require the user to authenticate to use the gateway via Proxy Authentication. Denying non-valid users. Initially allow all users who authenticate with username <phonenumber>@[login to view URL] with a configurable password. 3. Subscriber ID to Portals for personalization - The gateway will add a new header to the HTTP passed on to the sites. This header will include the user’s username, and will be this format:- ITdM-User: <phonenumber>@[login to view URL] 4. The gateway will use a list of valid and invalid sites that the user can visit. The user will get a Deny message for attempting to visit a non-authorized web site. 5. Redirects. There will be a list of sites that will be redirected without user knowledge. E.g. [login to view URL] -> internal web site. These can be contained within a config file of from->to and may be partial or full URL redirects. E.g. we may not just want [login to view URL] -> a.b.c.d we may want [login to view URL] -> a.b.c.d/anotherapplication. 6. WAP 2.0 as well as legacy WAP 1.2.1 standards 7. HTTP 1.0 and HTTP 1.1 8. SSL 2.0, SSL3.0 and TLS1.0 9. X.509 certificates 10. 128-bit encryption 11. WTLS 1.2 for secure mobile-device to gateway communications 12. TLS, SSL for secure gateway-application server communications 13. Certificate Requester for Gateway Certificate Chaining 14. RSA as well as ECC algorithms supported 15. Support for multiple languages 16. Cache implementation as defined by HTTP Caching (RFC 2616) 17. Smart caching will pre-fetch the content from web-server before client giving request 18. Cookie support as defined in HTTP State Management (RFC 2109) 19. Cookie Proxy support for passing of HTTP headers between the user agent and the origin server without interference. 20. Cookie Proxy support for Cookie Management and Storage functionality 21. Cookie Proxy support for user agent role in HTTP State Management Mechanism 22. Cookie Proxy support for WAP specific HTTP State Management headers and mechanisms 23. Supports WML, WMLC, WMLScript, WML1.1/1.2/1/3,WML2.0, mHTML ,xHTML. 24. Highly Configurable logging and audit trace levels 25. Log rotation done periodically 26. Support for large content object Using SAR ( Segmentation and Reassembly) and extended SAR 27. Bearers : IP based Bearers ( CSD, GPRS, CDMA, TDMA) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Linux Will use Apache 2.x as base to build gateway on. Mod_Perl should be the language used for building all functionality.