locked
Can't see profile image or details when at work RRS feed

  • Question

  • A picture is worth a thousand words, so to spare myself some writer's cramp:

    This is what I see at home:

    And this is what I see at work:

    I examined the page source when on my work network, and I didn't even see any <img> tags where my picture should be... Does social.technet.microsoft.com serve different pages to users requesting from certain networks? I'm kind of at a loss. The only other thing I can think of is that maybe the picture comes through via CSS somehow (odd way to do it). If so, what CSS file address do I need to tell our network people to stop blocking?

    Thanks for your help...


    Brandon Murray | MCTS | SharePoint Administrator

    Thursday, February 9, 2012 3:13 PM

Answers

  • Thanks Brandon!

    After looking at the Fiddler trace, there is definitely a proxy between your machine at work and our site. When attempting to load some of our site, you are recieving an HTTP 407. From Wikipedia:

    407 Proxy Authentication Required
    The client must first authenticate itself with the proxy.

    It is possible that the proxy is filtering one of our domains for some reason. For performance reasons, we host some of our content on:

    s-msft.com 

    This domain is owned and operated by Microsoft. My recommendation is to work with your IT department to ensure that this domain is not being blocked or filtered in any way. 

    Please let me know if you have any other questions.

    I hope this helps!


    Tim Shakarian, Software Developer

    Saturday, February 11, 2012 8:48 PM

All replies

  • The images or more specifically the widgets we use to display the image/name etc., are served dynamically from a central profile system, vs. directly from the forums. I'll grab some info from our operations team as to where this is being served specifically from.
    Thursday, February 9, 2012 4:31 PM
  • Thank you for bringing this to our attention Brandon. If you're willing, it would be very helpful if you could give us a Fiddler trace (http://www.fiddler2.com/fiddler2/) or take a screenshot of the network calls being made using the IE developer tools (F12->Network->Start Capturing, then refresh the page). If you need more detailed instructions please let us know.

    Thanks,

    Tim


    Tim Shakarian, Software Developer

    Thursday, February 9, 2012 5:16 PM
  • Sure, I've got a Fiddler trace with me right now. How would you like me to send it to you?

    Brandon Murray | MCTS | SharePoint Administrator

    Thursday, February 9, 2012 8:25 PM
  • Great! Please zip it and send to tshak [AT] microsoft [D0T] com.


    Tim Shakarian, Software Developer

    Friday, February 10, 2012 1:07 AM
  • Trace sent. Thanks Tim!

    Brandon Murray | MCTS | SharePoint Administrator

    Friday, February 10, 2012 4:56 PM
  • Thanks Brandon!

    After looking at the Fiddler trace, there is definitely a proxy between your machine at work and our site. When attempting to load some of our site, you are recieving an HTTP 407. From Wikipedia:

    407 Proxy Authentication Required
    The client must first authenticate itself with the proxy.

    It is possible that the proxy is filtering one of our domains for some reason. For performance reasons, we host some of our content on:

    s-msft.com 

    This domain is owned and operated by Microsoft. My recommendation is to work with your IT department to ensure that this domain is not being blocked or filtered in any way. 

    Please let me know if you have any other questions.

    I hope this helps!


    Tim Shakarian, Software Developer

    Saturday, February 11, 2012 8:48 PM
  • I just noticed something else in the trace. There is another domain that is also being blocked that could cause issues on many of our sites, as well as other sites on the internet:

    ajax.aspnetcdn.com

    This domain is also owned and operated by Microsoft. It is used for sharing popular JavaScript libraries. You can learn more about this service here: http://www.asp.net/ajaxlibrary/cdn.ashx.

    Thanks!



    Tim Shakarian, Software Developer

    Saturday, February 11, 2012 9:03 PM
  • Thanks Tim, I will report these addresses to our network ops team and see if it fixes the problem...

    Brandon Murray | MCTS | SharePoint Administrator

    Monday, February 13, 2012 3:49 PM