The "real" client, rather than for the apache client it talks to It is being proxied, and to configure it to produce content appropriate for The best plan is to make sure the origin server knows how Server to be modified to be sensible from the eventual client's perspective Or the mod_rewrite RewriteRule flag will be needed.Īnother thing likely to be needed is for the content produced by the origin ![]() Itself, and when it should act as a proxy server for s3. In order for it to work, apache needs to know when it should serve something In this case, s3. happens to be the same as s2., but To s3.:8080 - if that isn't the case, it becomes much easier. I'm assuming above that the client should never know about or connect directly Generated by apache -> content returned to client by apacheĬlient -> s2.:80 -> received by apache -> apache becomesĪ client to s3.:8080, which generates and returns content to apache If I understand things correctly, the intention is thatĬlient -> s1.:80 -> received by apache -> content To use AOL's ISP service on Linux, one must reverse engineer the authentication ![]() BeforeĪuthentication, a user's network traffic cannot reach the internet. It then establishesĪ TCPIP connection to authenticate the user. Protocols (PPP, PPPoE) to establish link-layer connectivity. Modern AOL software for Microsoft Windows uses standard Submit comments about articles, or articles themselves (after reading our guidelines) to The Editors of Linux Gazette, and technical answers and tips about Linux to The Answer Gang. ![]() UPDATES from previous HELP WANTED: Article
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |