Forum Discussion

Anas_Hijjawi_44's avatar
Anas_Hijjawi_44
Icon for Nimbostratus rankNimbostratus
Sep 18, 2011

Problem when submitting form of sharepoint using https

Hi, Please find my problem below if any one can provide a solution:

 

 

our F5 LTM is doing load balancing and SSL Off-Loading for our sharepoint servers but we are getting the following error when we try to submit any "FORM" using https only, but ate the same time it is working fine with http.

 

 

The error:" The form cannot be submitted to the Web server either because your computer is offline or because the host server is currently unavailable. I this problem persists, contact your network administrator."

 

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Hi, a common problem with offloading SSL in SharePoint are the Alternate Access Mappings. Generally you should add internal URLs for https:// first, then http:// for each of the hostnames you are using for the site. Are your AAMs configured correctly? Do you see any other strange behavior in the site, like pop-out menus or documents failing to load?

     

    thanks
  • Thanks for your reply, I reconfigured the AAMs and the form is submitted correctly, but the thing now is that for the infopath when we are using the application it working fine, but through the browser it is not, it is giving an error that you are not authenticated or the server is not available
  • do we need to configure the AAMs for every application -like such as infopath- or for the home page of the sharepoint only
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    You should do AAMs for every application that you access through the BIG-IP virtual server that is doing the SSL offloading.
  • Like Infopath is part of the sharepoint, so we need to do a different AAM for it, this is what you mean right?
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    If you were accessing Infopath via a separate URL, you would need to do an AAM for it. If you didn't already have a separate internal URL, then you wouldn't. I would try a packet capture between the client and BIG-IP while using both the InfoPath application and a web browser, and compare them to see what may be breaking the connection. F5 support can assist you with that.