my json url has an API key which I don't want it to be shown to the user?
is it possible to encrypt it or hide it?
The simplest option is probably to create a page on your site which loads the data from the remote service and echoes it directly to the response. That way, your script can call a page on your site without having to pass the API key.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
A simple asp.net page: GridView in an UpdatePanel with a timer to refresh the data every minute.
Works Fine On My Machine, hitting IIS Express.
Doesn't ever refresh when deployed to the actual IIS server. It just sits there and laughs at me.
I've tried various combinations of Timer outside the UpdatePanel with the AsynPostBackTrigger set, Timer inside UpdatePanel with no trigger set. Timer tick explicitly saying to update the UpdatePanel. Etc etc etc, just like the two million Google hits suggest, to no avail.
Every "fix" works fine on my machine.
It just refuses to work on the server.
Is there an IIS setting of some sort that might be causing it? Elsewhere on the page (outside the UpdatePanel) is a Panel with the CollapsiblePanel extender tacked on which works fine, so it isn't a matter of Ajax not being there. Looking at the webpage source from the server and from VS, I see no differences other than the extra crap VS puts in when hosting.
<asp:TimerID="Timer1"runat="server"OnTick="Timer1_Tick"Interval="60000"Enabled="true"EnableViewState="False"></asp:Timer><asp:UpdatePanelID="UpdatePanel1"runat="server"ChildrenAsTriggers="false"UpdateMode="Conditional"EnableViewState="False"><Triggers><asp:AsyncPostBackTriggerControlID="Timer1"EventName="Tick"/></Triggers><ContentTemplate><asp:LabelID="lblLast"runat="server"Text="Newest Order: (waiting for update)"EnableViewState="False"></asp:Label><asp:LabelID="lblStatus"runat="server"Text="Checking for orders..."Visible="False"EnableViewState="False"></asp:Label><divclass="Refreshed"><asp:LabelID="lblRefresh"runat="server"CssClass="Refreshed"Text="Last Refreshed:"EnableViewState="False"></asp:Label></div><br/><asp:GridViewID="grdStatus"runat="server"AutoGenerateColumns="False"CellPadding="4"ForeColor="#333333"Width="100%"CssClass="Grid"EnableViewState="False">
There are some HTML content which designers has barely control over.
For instance, laying out checkboxes requires a lot of tricks (as far as I know).
Without those tricks, checkboxes can really mess the layout.
For instance (I hope it'll help showing my point) I once had a page having parts using a very big high font-size and having a few checkboxes. On many browsers, the font-size didn't cause a scale of checkboxes. Thus side to some huge text were normal (microscopic looking) checkboxes.
With new inputs like "range", "date", etc. there are now many new element which one doesn't have css control over.
Thus I'm wondering if I should avoid using such inputs.
Or maybe am I missing an important point.
You could take a look at "range" for instance.
It display slightly differently on different browser.
And you can't set its height in firefox for instance.
So if you make a page whose sole/main purpose is to set a ranged value. And wish to make the slider bigger (the bigger it is, the easier it is for the end user) you actually can't.
Same would go it you were using a checkbox.
I've seen now what are you talking about. I thought you have problem with HTML 5 itself, but it's clear that the problem is with implementation in different browsers.
There is nothing - except opening bug report with the browsers - you can do about it.
HTML 5 is still in 'Candidate Recommendation' state, so things can change...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
I have seen the tiny check-boxes, myself, on IE8 (most of people here still use that). As you've heard, time and again, IE doesn't play well with others. I've also had layout problems on local vs. thin-client views using the same browser (IE8 or latest FireFox).
One solution I've been forced into is most layouts are now done with position:absolute. In particular, sized and position designated by % were troublesome.
Check-box layout hasn't been a problem, even when created by AJAX. A desperate solution to the positioning could be to create a
element to contain your check-boxes, each in it's own column;
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
Complex types by default are resolved from the Body of request, which a Get doesn't use.
changing the parameter to an integer id
of the parameter to [FromUri] GetDaysForAssignmentEntity entity)