SharePoint will work through webNetwork, but there are a few issues.
SharePoint really is designed for a full MS environment, if you are not using IE, you may lose some functionality.
There are a few Microsoft URLs that should be referenced.
Microsoft SharePoint Team Blog
What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)*
* parts 2 and 3 of this blog have since been removed from the Microsoft SharePoint blogs.
Plan alternate access mappings (Office SharePoint Server)
What Every SharePoint Admin Needs to Know About Host Named Site Collections
These documents explain how to set up SharePoint to work through a proxy server.
This tells SharePoint that you will be connecting to SharePoint on a different
name than the normal name. This name will be the name used in the webapp
virtual dns name. SharePoint uses this to generate urls on the web page.
For example. Normally on the LAN the user type http://sharepoint/ to login to SharePoint.
This obviously will not work on the internet because it won't know what you mean by http://sharepoint.
You will also probably want to secure SharePoint with SSL. So to let webNetwork handle the SSL, we have to tell SharePoint to respond on some new names.
To use the example from the MS blog, replace
https://www.conteso.com with https://wnsharepoint.example-cloud.com
and
http://sharepoint.dmz.contoso.com with http://intsharepoint.example-cloud.com
This means that in webNetwork we are going to make a Host object that points to
instsharepoint.example-cloud.com on port 80 Then the virtual webapp sets up a virtual
dns name of wnsharepoint.example-cloud.com. By setting the Host Authority to
disabled, the user talks to webNetwork with https://wnsharepoint.example-cloud.com and
webNetwork in turn talks to SharePoint with http://intsharepoint.example-cloud.com.
SharePoint sees that and knows when it sends back the information, it should
format the pages with https://wnsharepoint.example-cloud.com