britishdeveloper.co.uk Report : Visit Site

Technical data of the britishdeveloper.co.uk

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host britishdeveloper.co.uk. Currently, hosted in United States and its service provider is GoDaddy.com LLC .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called GSE containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

skip to main | skip to sidebar a blog about microsoft's web development technologies written by a brit. mainly asp.net mvc c# entity framework azure visual studio and sql find a location for property in a new city wednesday, 7 december 2016 reference object with ref keyword on a method. what's the point? i wondered the other day what the point is in making a method parameter a ref when it is already a reference type. after playing around for a bit i came up with some concise code to illustrate the difference. the difference is that, although you can modify the reference object that was passed in with both methods. changing the reference entirely (i.e. pointing to a different object) only has an effect outside the scope of the method if the object was passed through with the ref keyword. this code should explain better than english: void main() { var t1 = new thing(); test(t1); t1.write(); // chair var t2 = new thing(); test(ref t2); t2.write(); // table } void test(thing t) { t.name = "chair"; t = new thing { name = "table" }; } void test(ref thing t) { t.name = "chair"; t = new thing { name = "table" }; } class thing { public string name { get; set; } public void write() => console.writeline(name); } posted by colin farr at wednesday, december 07, 2016 30 comments labels: c# share to twitter tuesday, 22 december 2015 stop processing options requests for cors in asp.net web api i was attempting to allow some particular origins to access my asp.net web api from a client side single page application. i was using the enablecorsattribute that comes with the microsoft.aspnet.webapi.cors nuget package. i managed to set up cors using the following code in my webapiconfig: var origins = configurationmanager.appsettings["allowedorigins"]; var cors = new enablecorsattribute(origins, "accept,content-type,origin,customid", "get,post,put"); config.enablecors(cors); there is quite a lot to cors but essentially, (some browsers) send a pre-flight request recognised with its http method options. this basically asks the application who is allowed to access this url with the attempted headers and http method. your web api will respond saying which origins are allowed or if there are any errors. the browser then decides if it is one of those allowed origins and sends the request if it is. the problem i found is that on this initial options request my ioc container, unity, was constructing a whole dependency chain of classes. some of which access the database and some check http headers. this was throwing an error since bits were missing from the http headers that would be with normal requests and unnecessarily hitting the database. so really, i wanted to stop these requests in their tracks whilst making sure they did their intended pre-flight work. the best way i found to do this was to ignore routes based on an http constraint for "options". basically shove this in your routing: var constraints = new { httpmethod = new httpmethodconstraint(httpmethod.options) }; config.routes.ignoreroute("options", "{*pathinfo}", constraints); more info on enabling cors in web api . posted by colin farr at tuesday, december 22, 2015 26 comments share to twitter thursday, 6 august 2015 outbound ip address from azure webjobs or website i need to find the outbound ip address of an azure website so that i can whitelist this ip address in a service i wish to call. however there are concerns with this practice as i will explain. azure webjobs are completely awesome and they should be used more. i have project however that i am using to pre-process a large amount of data. as part of this process, my web job will need to call a third party web service that operates an ip whitelist. so to call it successfully i need to find the ip address of my azure webjob. that is simple enough, i confirmed the ip address using two sources, one is a given list of ip's as documented by microsoft. details on how to find yours are here: azure outbound ip restrictions . i also wrote a little code to make sure this matches from a webjob like so: public async static task processqueuemessage( [queuetrigger("iptest")] string message, textwriter log) { using (var client = new httpclient()) { var response = await client.getasync("http://ip.appspot.com/"); var ip = await response.content.readasstringasync(); await log.writeasync(ip); } } popping something in the "iptest" queue kicked off the job and checking the logs confirmed the webjobs are in fact consistent with the ip ranges documented. there is a problem however, if you read that link you will discover that although it is roughly static it is not unique. you will share your outbound ip with other users of azure websites that are hosted in the same region as you and the same scale unit as you. what is a scale unit? who cares but there are 15 of them in the north europe data centre for example so not a lot. now how secure do you think ip whitelisting a shared ip is? not very! workaround don't give up hope! the work arounds i can see are to ask the service provider to not rely on only ip whitelisting, have another form of authentication, an api key over ssl would work for example. have it as well as ip whitelisting if it makes them happy. if they can't be controlled you can do your own magic. there are proxy providers out there that will provide your calls with a unique static ip address. try quotaguard . or make your own - if you already have a cloud service running in azure you can proxy the service via that as they can have static and unique outbound ip addresses. posted by colin farr at thursday, august 06, 2015 19 comments share to twitter skipping unit tests is a false economy you only need unit tests if you write buggy code but why would i write bugs? i don't need them. for a long time i thought unit tests was just vanity code. oooh look, i've made this repository unit testable and i've used my fav' ioc container to inject dependencies now so in my tests i mock them to create and elegant suite of unit tests. no one will ever run the tests but it is cool because all the top dev bloggers write about it. that is probably a lot of people's motives, that and the lead dev told them to. you can tell when people don't fully understand why they are writing unit test when they are running short of time to complete their work and the first thing they compromise is the unit tests. unit tests are always the first to be dropped in high pressure environment. let me sell unit tests to you they save you time! how can that be right? they take so long to write and refactor every time you change your code. unit tests save you time because you no longer need to trawl through mountains of code to work out in you head any possibility for causing a bug. you don't need to step through every line of code in your application finding potential for unexpected consequences when you have decent unit test. which saves so much time! worse still is the people that wouldn't have trawled through the code to find a potential bug and just committed their code anyway and broke something. sooner or later it will get noticed and someone is going to spend a very long time tracking it down and then fixing the root cause. what about deployment time as well, when you come to merge and commit a branch or do a deployment, how long would it take you to review every line in the merge or click about every section of the site? 30mins? hours? or maybe you wouldn't bother and as mentioned that is when the even harder to find bugs creep in. it is such a waste of time! writing unit test from the beginning will slash all this wasted time! unit tests should be the first things your write! this is called tdd (test driven development) and it is the most effective way of ensuring your tests get written as you can't drop them out to save time as they are already written. it also forces you to really think about your code before writing it. but tdd or not, please please write them. lots of them. use ncrunch that has

URL analysis for britishdeveloper.co.uk

http://www.britishdeveloper.co.uk/2010/10/
http://www.britishdeveloper.co.uk/search/label/security
http://www.britishdeveloper.co.uk/#sidebar
http://www.britishdeveloper.co.uk/search/label/delete
http://www.britishdeveloper.co.uk/search/label/ajax
http://www.britishdeveloper.co.uk/search/label/ssl
http://www.britishdeveloper.co.uk/search/label/software
http://www.britishdeveloper.co.uk/2011/08/
http://www.britishdeveloper.co.uk/search/label/.net4
http://www.britishdeveloper.co.uk/2013/01/
http://www.britishdeveloper.co.uk/search/label/release%20date
http://www.britishdeveloper.co.uk/2016/12/ref-parameter-on-already-reference-type.html
http://www.britishdeveloper.co.uk/2013/01/handler-extensionlessurlhandler.html#comment-form
http://www.britishdeveloper.co.uk/search/label/funny
http://www.britishdeveloper.co.uk/search/label/azure%20storage

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Error for "britishdeveloper.co.uk".

the WHOIS query quota for 2600:3c03:0000:0000:f03c:91ff:feae:779d has been exceeded
and will be replenished in 2163 seconds

WHOIS lookup made at 16:14:22 23-Jun-2018

--
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:

Copyright Nominet UK 1996 - 2018.

You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REFERRER http://www.nominet.org.uk

  REGISTRAR Nominet UK

SERVERS

  SERVER co.uk.whois-servers.net

  ARGS britishdeveloper.co.uk

  PORT 43

  TYPE domain

DISCLAIMER
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:
Copyright Nominet UK 1996 - 2018.
You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REGISTERED no

DOMAIN

  NAME britishdeveloper.co.uk

NSERVER

  NS50.DOMAINCONTROL.COM 173.201.72.25

  NS49.DOMAINCONTROL.COM 216.69.185.25

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .